41–50 of 51 posts
I've been a big firefox fan since phoenix, but already moved to chrome for only one reason: Fastest...browser...evar
I've been a big firefox fan since phoenix, but already moved to chrome for only one reason: Fastest...browser...evar
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.
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.
Editing style rules applied to elements: yes, you can do this. Select an element in the inspector, and you can click to edit its style rules.
Earlier quoted context omitted.
They'll never have Tree Style Tabs I imagine, so I'm stuck forever with Firefox for that extension. Not that I mind Firefox, but Chrome gets to do a reboot and start again without carrying legacy support/etc with it. Early versions of Firefox felt "lighter" than IE to me for that reason.
Remember when Firefox was the lightweight web browser? Of course it was called Phoenix back then, and later Firebird. It was refreshing.
It's probably only got more "lightweight" with time as they've had more opportunity and funding to optimise and actually remove things they don't use.
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.
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.
Works for me. In preferences, manage search engines. All or most of the search engines you've used in the past should be there. Edit the keyword to the keyword of your choice (for Wikipedia I use "wp"). In the omni bar, type "wp", space, query, enter. Alternatively you can use a tab instead of a space and this makes it more obvious that you are searching.
Close the browser. Reopen. Check the options again. (Still there.) Type wp (so far so good, the Chrome hints drop-down looks like I'm going to hit Wikipedia) space, "San Francisco" (no quotes) ... and oops, the hints have changed to "Google Search" (as soon as I type the first character.
Earlier quoted context omitted.
Works for me. In preferences, manage search engines. All or most of the search engines you've used in the past should be there. Edit the keyword to the keyword of your choice (for Wikipedia I use "wp"). In the omni bar, type "wp", space, query, enter. Alternatively you can use a tab instead of a space and this makes it more obvious that you are searching.
OK, so I update my search preferences to make "wp" the Wikipedia key word. (I think, ok, maybe "w" was too short or something.) Close the browser. Reopen. Check the options again. (Still there.) Type wp (so far so good, the Chrome hints drop-down looks like I'm going to hit Wikipedia) space, "San Francisco" (no quotes) ... and oops, the hints have changed to "Google Search" (as soon as I type the first character.
Earlier quoted context omitted.
OK, so I update my search preferences to make "wp" the Wikipedia key word. (I think, ok, maybe "w" was too short or something.) Close the browser. Reopen. Check the options again. (Still there.) Type wp (so far so good, the Chrome hints drop-down looks like I'm going to hit Wikipedia) space, "San Francisco" (no quotes) ... and oops, the hints have changed to "Google Search" (as soon as I type the first character.
That's puzzling. Don't know if it will help, but for reference I'm running the dev channel build on OS X.
Hey I realize most of you guys like the single omni-box, (I consider it a waste of real estate), but at least make the second FireFox/IE type search box optional. Let the user decide.
Earlier quoted context omitted.
Hasn't got what polish of Firefox? Firefox is buggy and has a kludgy UI. Chrome is way more polished.
Selecting multiple blocks of text. Scrolling with the mouse wheel. / for quick find (and ' for links). 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.…