Live data from Hacker News

The future Firefox UI

people.mozilla.com

91–100 of 191 posts

Re: The future Firefox UI

#91
post #54

The dev tools' UI[1] looks amazing . http://people.mozilla.com/~shorlander/devTools/devTools.html

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

http://blog.mozilla.com/devtools/2011/05/25/the-relationship...

tldr; no. Firebug is an independent (but with Mozilla's support and blessing) project and we're also building some great tools that will ship with the browser.

Re: The future Firefox UI

#92
post #88

Earlier quoted context omitted.

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.

You will not be annoyed. Promise :)

Re: The future Firefox UI

#93
post #56

Earlier quoted context omitted.

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.

Good to know. I should give it a try.

Re: The future Firefox UI

#94
I'm hoping they will do away with the "you need to restart Firefox after installing an add-on". Chrome has been able to install/uninstall/disable/tinker with add-ons without the need to restart for years. That and a new logo (tired of that fox) and I may give it another try.

Re: The future Firefox UI

#95

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…

> What I don't like about these Chrome UI's is that they don't respect my OS settings Hear, hear. On our new serious workstation, we mostly run a variety of developer tools and browsers, some basic office software, various graphics/DTP/modelling stuff from companies like Adobe and Autodesk, and a bunch of tools to automate things and join the dots. On a quick look, exactly none of the major products there uses the st…

> I wish Microsoft would define a robust, standardised set of UI conventions again, based on usability rather than flashy stuff, and then at least stick to it themselves instead of inventing a whole new bunch of tricks for every new version of Office, IE, Visual Studio and so on.

This, to me, is one the biggest pluses for Macs at this point. Microsoft keeps trying to reinvent the GUI, but they don't get rid of the old stuff, even in their own systems.

I also wish Microsoft would adopt actual application bundles. 99% of applications should not actually need installers and uninstallers. Despite what Raymond Chen says, a simple folder is not the same thing.

Re: The future Firefox UI

#96

I'm hoping they will do away with the "you need to restart Firefox after installing an add-on". Chrome has been able to install/uninstall/disable/tinker with add-ons without the need to restart for years. That and a new logo (tired of that fox) and I may give it another try.

I promise you the fox isn't going anywhere, but add-ons made with the new APIs don't require restart.

Re: The future Firefox UI

#97
post #17

Why has Firefox been so slow to slim down its UI? The back button is still way too big and the button colors not subtle enough. A browser should disappear into the background to some extent. It's just a window into the interwebs after all.

The back button is intentionally bigger as it is one of the most used buttons in a browser. In accordance with Fitt's law, the size allows a user to get to it quicker than a smaller button.

Re: The future Firefox UI

#98
post #22

Glad they finally copied Chromium. Would be great if they copied it too with regards to startup speed and JS execution speed.

Firefox 8 nightlies are as fast if not faster than the Dev Channel build of Chrome 14.

Re: The future Firefox UI

#99
post #69

Earlier quoted context omitted.

Actually, you do: In Chrome, you can turn off search autocompletion for the top bar. It will search history and bookmarks, but not contact Google.

Which all of 0.0003% of people will actually turn on. It's not so much about me not knowing what is being sent, it's about anything users across the web type into the url box is sent to servers somewhere. It's not information companies need to know, anonymous or not.

I was mainly offering that to address jbk's personal concerns, and agree that as a default setting, it constitutes an unexpected information/privacy leak for most users.

Re: The future Firefox UI

#100
post #80

While this does look very pretty I'm kinda concerned that they're throwing a lot of good stuff away. I'm running Firefox 5 and it really feels polished, there's so many things I'm still discovering and thinking "hey, that's cool". It's a feeling you most often get when a design has been iterated, and tweaked, and worked on for a long time... I get the same feeling frequently on the Mac I have to use at work. This is…

> In particular, vertical pixels are at a premium for me, and Firefox 5 has done a lot to improve this... this is a step backwards, as the main bar at the top is larger.

Really? Looks like an improvement to me, because tabs have now consumed the titlebar area. The tab area itself is larger, but the total change is a reduction in the amount of vertical space used.

> And seriously, those curves take up a ridiculous amount of real-estate - compare those tabs to Chrome or FF5, how many can you get on your screen?

The curve is only on the active tab, so I don't see how it's reducing the amount of tabs you can have.

Post reply on HN