31–40 of 51 posts
Is the Chromium UserScripts page[1] out of date? Or are these still issues? Chromium does not support @require, @resource, unsafeWindow, GM_registerMenuCommand, GM_setValue, or GM_getValue. A lot of scripts that I come across use `unsafeWindow`, `GM_setValue` and `GM_getValue.` It seems to be updated (since the last time I looked at it), since I believe it used to say that @exclude was not implemented, and now I don'…
Earlier quoted context omitted.
Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.
The element inspector is handy, but personally I would also need JavaScript step through debugging like Firebug provides.
It has a great DOM inspector (allows editing), network/script/rendering timeline, step-through debugger, profiler, cookie and local database inspector, and Chrome even has a heap analysis tool (see which objects are allocated).
It's far better than Firebug, at least for JavaScript developers, IMO.
I only wish Chrome would add a second search box, like IE and FF do. I have never figured out how to get the keyword for another search engine (Wikipedia) to work satisfactorily in Chrome's combination url/search entry area.
I wish all other browsers would drop the unnecessary secondary box when they could be doing the searching in the address bar like Chrome.
That feature could seriously be a deterrent for switching away from Chrome or Firefox.
Earlier quoted context omitted.
Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.
The element inspector comes somewhat close, but you can't add css attributes to selectors, only modify existing ones, which really makes the thing useless when doing front end dev
Earlier quoted context omitted.
The element inspector comes somewhat close, but you can't add css attributes to selectors, only modify existing ones, which really makes the thing useless when doing front end dev
Are you sure? I think you can edit the text of stylesheets, and add new style properties on individual elements too.
Does not anyone else get really let down every time they read a Chrome submission that doesn't announce that Firebug has been ported over? I've started using Chrome for my day to day browsing, but I'll never be able to wholeheartedly switch until Firebug arrives.
Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.
Earlier quoted context omitted.
Likewise, on both points. It hasn't got the polish of Firefox, and the extension ecosystem is a little rough, and I miss the intelligent URL completion from the Awesomebar, but Chrome wins in speed and stability, and those were enough to move me away from Firefox for all but a few sites. Speed is important.
Hasn't got what polish of Firefox? Firefox is buggy and has a kludgy UI. Chrome is way more polished.
edit: I wonder if this is similar to the difference between Windows and Mac. Windows might be inconsistent in the small things (e.g. button padding), but it gets the large things right. Mac gets the small things right but the large things horribly, horribly wrong. Chrome seems to get the small things right too (e.g. tab animations), but overall Firefox does much better.
I always thought Google had a browser for the masses in mind with Chrome. Something that is easy to use, stable and fast: a good alternative for IE. User scripts are something for power users, who will always prefer Firefox. Won't this create the risk that average users will accept installing all kinds of scripts without much regard for security implications? User scripts are a powerful yet low-threshold tool which c…
> power users, who will always prefer Firefox Why do you say that? Chrome has extension support, I'm not sure what unique feature Firefox will have left shortly.
Is the Chromium UserScripts page[1] out of date? Or are these still issues? Chromium does not support @require, @resource, unsafeWindow, GM_registerMenuCommand, GM_setValue, or GM_getValue. A lot of scripts that I come across use `unsafeWindow`, `GM_setValue` and `GM_getValue.` It seems to be updated (since the last time I looked at it), since I believe it used to say that @exclude was not implemented, and now I don'…
Earlier quoted context omitted.
Are you sure? I think you can edit the text of stylesheets, and add new style properties on individual elements too.
unless you're seeing something I'm not seeing, you can only modify existing attributes. If you could show me though, an upvote will be in your future :-)