Live data from Hacker News

The future Firefox UI

people.mozilla.com

151–160 of 191 posts

Re: The future Firefox UI

#152

Earlier quoted context omitted.

I'll admit I am not a good pick when it comes to computer semantics, so I might be mistaken. Trying to be an "app" or not: For me, it is about the courtesy of respecting my main OS settings. It is about introducing accessibility concerns by overriding system settings such as demonstrated in this active bug report from 2008: http://code.google.com/p/chromium/issues/detail?id=92 > They aren't going to, and shouldn't, w…

My point wasn't that they shouldn't fix bugs; it's that they shouldn't prioritize fixing OS-specific bugs that impact 0.2% of their users. It sounds like you are a Windows power user and I suggest you use IE9 instead.

I'm pretty sure more than .2% of Chrome users use Windows.

Re: The future Firefox UI

#153
post #18

Earlier quoted context omitted.

I don't know, that floating button in the top left bugs me in linux. It makes sense in windows because it just blends in with the tabs next to it, but in linux it's on its own line with the tabs showing up below it. The wasted space annoys me to the point that this is one of the main reasons why I do not use Firefox anymore.

I'm not sure what you're referring to. On my computer, it looks either like [this]( http://i.imgur.com/jZiFO.png ) or [this]( http://i.imgur.com/yHMKH.png ). No "floating button in the top left" either way.

http://i.imgur.com/d4jjL.png

Re: The future Firefox UI

#154

Earlier quoted context omitted.

Dramatic decisions are often criticized until people accept it and adapt. I remember reading about how consumers wouldn't be able to adapt to a touch screen phone that didn't have a keyboard option.

Sometimes what actually happens is that people get used to the change and get tired of fighting against. But they still don't like it at all. It's hard to see the difference from outside.

Exactly. Someone might have their leg amputated and complain for a while, then eventually accept it and adapt. This does not mean that having a leg amputated is a good thing.

Re: The future Firefox UI

#155

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…

And it's not like Microsoft haven't done the same - the ribbon and that bulbous Office button for saving and opening confuse me every time.

Re: The future Firefox UI

#156
post #67
post #28

Earlier quoted context omitted.

Be faster than Chrom(ium) with regards to start up speed and JS execution. I abandoned FF after having used it since it was "Phoenix 0.1", because it had become slow and bloated, like NN had been before. Would love to switch back, but not if I can open 5 Chromium instances in the same time it takes to open one FF window.

Have you tried a new profile? A long-time user will end up with a really crufty Firefox profile. Sync will move all your data to a new profile quickly and you can see what a new profile in Firefox is like.

Sync will not move all your data. I switched to a new profile after installing an add-on that introduced problems and uninstalling didn't correct those problems. I fell back to Sync for the new profile so I could salvage my history and bookmarks from my 2-ish year old profile, but it left out something like 9 months of history, all but two of my tags, and a good chunk of my bookmarks and search keywords (including the ones I'd set up for MXR).

I'm not sure if it was buggy, or if Sync was intentionally not tracking the stuff that didn't get copied over. (cf mconnor's blog post a month or so ago about implementing Sync quota caps).

Re: The future Firefox UI

#157
post #148

Earlier quoted context omitted.

For people who care about such things, you can customize the toolbar and enable "Small Icons".

It's always the first thing I do but unfortunately defaults matter.

Sure, but many like the current default -- on a netbook, I used small icons, but everywhere else I willingly sacrifice a couple of pixels for an easier target.

Re: The future Firefox UI

#158
post #124

Earlier quoted context omitted.

If you think about it, the forward button is disabled about 80% of the time -- so it doesn't really need to always be there. The forward button isn't being removed completely; it'll just be hidden when it's not clickable. It will slide out when there's a "forward" URL available.

Ugh. I hate shapeshifting UIs. Muscle memory depends on stuff being fixed in space relative to other elements.

muscle memory is less relevant when mousing. the range of starting positions is large.

Re: The future Firefox UI

#159
post #48

Earlier quoted context omitted.

The whole app feels like an imitation of a Mac app. Most obviously on 10.7, the window chrome is wrong. Other small things like incorrect and wrongly sized fonts inside controls, or the whole menu bar disappearing when you use an extension in its own window. When you add everything together, it just feels wrong, like wearing clothes that don't fit. The way they've been updating the UI so far has seen some improvement…

> or the whole menu bar disappearing when you use an extension in its own window Could someone explain to me the correct way for a developer to handle this? I've been aware of this problem for a while, and I've newly come to own a Mac, so I've looked into it more and looked at what other apps are doing. There doesn't seem to be a correct solution. I looked at how Safari handles the Web Inspector, and it just adds a n…

I think the solution that Apple would suggest is to just not put an "app-within-an-app". If the feature set is far enough apart that it feels like a separate app that needs a separate menu bar, it should be a separate app.

(I actually agree: when is that ever better than a dedicated app?)

Re: The future Firefox UI

#160
Status bar 4 eva. I don't want "improved" UX, I want to keep it as is, and anyone who wants a new UX should opt in for that. Don't force me to look at your latest designer's attempt to be noticed.
Post reply on HN