I like that wallpaper. Does anybody have a link to that?
The future Firefox UI
151–160 of 191 posts
Re: The future Firefox UI
#152Earlier 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.
Re: The future Firefox UI
#153Earlier 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.
Re: The future Firefox UI
#154Earlier 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.
Re: The future Firefox UI
#155What 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…
Re: The future Firefox UI
#156Earlier 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.
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
#157Earlier 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.
Re: The future Firefox UI
#158Earlier 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.
Re: The future Firefox UI
#159Earlier 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 actually agree: when is that ever better than a dedicated app?)