Live data from Hacker News

The future Firefox UI

people.mozilla.com

81–90 of 191 posts

Re: The future Firefox UI

#81
post #35

Folk are focusing on the two changes that make this more like chrome (tabs in title bar, and apparent removal of search bar.) There's more going on here.[1] * Simplified, customizable graphical menus. No idea how well this will work, but it's only a mock-up at this point. * Removal of the forward button, merging the back button with the URL bar. * Refinement of per tab UI. In chrome you still get the browser chrome o…

I hope there's an option to put the forward button back in. I use it a lot.

Do you actually use the button itself rather than a mouse/keyboard shortcut?

Re: The future Firefox UI

#82
post #56

Earlier quoted context omitted.

Having a dedicated search box is my big beef with every other browser.

If Firefox adds a single bar for search and URLs, I'd consider switching back, especially if they do a better job of history search than Chrome. (Chrome's history search sucks pretty bad in my experience.)

firefox has an addon called omnibar that does exactly this.

Re: The future Firefox UI

#84

What I don't like about these Chrome UI's is that they don't respect my OS settings. I am on Windows 7 with the classic NT skin. iTunes and Chrome are one of the few programs that don't respect this skin. While in this case it is simple user preference, in other cases it could mean an accessibility concern, or even give room to malicious attacks: With all these custom browser skins, pop-ups over the HTML body (link d…

> users won't clearly know the difference between interaction with the browser, and interaction with a smart malicious website.

If you remove the word malicious I think this very fact is the future of browsers. The browser should be designed to prevent a developer from doing anything malicious, but they should fade into the background and allow the web developer to make many (all?) the UI decisions.

Re: The future Firefox UI

#85
It looks fantastic! Only thing I fear about firefox is the speed. (Speed at Starting, loading setting windows, obviously loading pages, caching, etc.)

Re: The future Firefox UI

#87
post #35

Folk are focusing on the two changes that make this more like chrome (tabs in title bar, and apparent removal of search bar.) There's more going on here.[1] * Simplified, customizable graphical menus. No idea how well this will work, but it's only a mock-up at this point. * Removal of the forward button, merging the back button with the URL bar. * Refinement of per tab UI. In chrome you still get the browser chrome o…

I hope there's an option to put the forward button back in. I use it a lot.

http://www-archive.mozilla.org/docs/end-user/moz_shortcuts.h... if you're in to that sort of thing... (some people prefer buttons, no judgement here.)

Re: The future Firefox UI

#88
post #54

Earlier quoted context omitted.

Are they going to fully integrate firebug into firefox rather than having it as an extension?

As I understand it (it's still somewhat in the planning stages, and things are evolving), Firefox will ship with a set of developer tools which will cover the major use cases (inspector, console, etc). Firebug will be an extension, and will add more advanced functionality. It's being rewritten in JavaScript, and could potentially work on any browser (Firebug and Firebug Lite are going to merge). This is how I underst…

PLEASE integrate these things carefully and in a sensible way. If I have to use "dev tools" for x, b, and z and firebug for a, y and c that's going to be annoying as hell.

Re: The future Firefox UI

#89
post #8
post #7

Wow. I really hope this isn't just speculation and something that's being put into production. Yeah, it looks like a Chrome clone, but it's been done well and with a slight twist. As a dedicated Chrome user, though, it's going to take more than just a coat of paint to get me to switch back. Can't wait to see where this ends up.

What would you want to see in another browser that would make it worth switching away from chrome?

The shortlist would be: speed, standards compliance, UI, and developer support (I love that Chrome has built-in dev tools -- I know firebug exists, but compared to CDTs, again, it seems clunky).
Post reply on HN