Linked by Thom Holwerda on Wed 23rd Sep 2009 22:31 UTC
We've already talked about the proposed interface changes for Firefox 3.7 (and 4.0) which are coming to the Windows platform. However, those were anything-goes sketches, and now it seems as if the team has more or less settled on what Firefox 3.7 will look like on Windows. I'll reserve final judgement until I have used it, but my first thought was: who littered all these different widgets all over the place?
Permalink for comment 385817
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-09-21
I'm sorry to say but this whole article is non-sense. Besides the fact the preferred interface looks depends on your personal liking and thus there is NO proper interface design for everybody, the differences between Firefox 3.7 and Google Chrome negligeable.
Not true at all. There are some objective criteria that makes the chrome UI much cleaner and more logical than the FF concept.
1. Tabs on top. The address, as well as the page controls are logically part of the page, and should within the tab rectangle. On FF, the address bar and back/forward are visually disconnected from each tab, as though they were constant across all pages, which they aren't.
2. Single address bar. Reduces clutter (one less widget) and many non-technical users don't know the difference between the address bar and a search bar. Many people type everything, including addresses into google. Also for advanced users it makes no sense to have two separate bars if one can do just as good of a job.
3. The Page and Tools buttons in the FF ui are completely different visual style than everything else. Consistency is a pretty fundamental aspect of UI design.
4. The frame around the tab and bookmarks bar in FF has no purpose and contributes to clutter. It also further isolates the address bar, separating it visually from the page content, even though it is actually connected to the page.