What's the green "tree" button to the right of the home button?
It's the favicon of a site that is pinned as an "app tab".
Makes sense. Thanks!
The future Firefox UI
121–130 of 191 posts
Re: The future Firefox UI
#122I'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 like the fox more than the pokeball.
Re: The future Firefox UI
#123Earlier quoted context omitted.
That's because you mistakenly think Chrome is a Windows app, a Mac app, and a Linux app. It's not. It's an operating system that runs on top of those. They aren't going to, and shouldn't, waste their time trying to mimic UI decisions for various OSes. They aren't trying to be like Seesmic or Evernote (meaning, they aren't trying to be an "app").
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
#124Earlier quoted context omitted.
I hope there's an option to put the forward button back in. I use it a lot.
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
#125Earlier 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.
The only element that would shift is the awesome bar, and that's a pretty big target to miss.
Re: The future Firefox UI
#126Earlier quoted context omitted.
Firefox's UI has always been the most customizable of any of the major browsers. You will be able to add it back in if it is taken out by default in the future. (Disclosure: I work for Mozilla but not on the UX team.)
I do not believe that, from my experience Opera is much more configurable, at least my current Opera setup suggests that. I have added buttons to my UI that I would have to install addons for in Firefox.
Well, he said major.
Re: The future Firefox UI
#127What 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…
Most of the native Mac OS X applications are made using XCode which comes with the same basic default menu each time you start a new project. That is a guarantee that most apps are going to adhere as much as possible with the OS's conventions. There are exceptions, of course.
How many different IDEs/toolkits are available and used to develop Windows or "Linux" applications?
Re: The future Firefox UI
#128i hope they roll this out gradually. one of the biggest things that makes people stick with old browser versions is a reluctance to move to a new UI. if they introduce a big change, we're going to see a whole bunch of people sticking with an old browser version for much longer than they should.
this is something that chrome is awesome for. they have changed the UI around a bit since v1, but each change has been so minimal that nobody has really noticed too much.
Re: The future Firefox UI
#129Folk 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…
The preferences menu is also very similar to Chrome's.
Re: The future Firefox UI
#130I don't understand why no browser manufacturer integrates tree tabs. It's such a great interface innovation, and everybody is just ignoring it.
Because to a user that barely understands tabs as it is, it's simply not going to fly. And yes, many nontechnical users do struggle with the idea of tabs.