Talk:Firefox/4.0 Windows Theme Mockups: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 66: Line 66:


--[[User:NoamNelke|NoamNelke]] 00:12, 28 July 2009 (UTC)
--[[User:NoamNelke|NoamNelke]] 00:12, 28 July 2009 (UTC)
== Is UI change really needed? ==
Is there really a need to combine the refresh/go/stop buttons?  Most people have plenty of horizontal space, and having separate single purpose buttons is a lot less confusing.
Also, why ditch the menu bar?  I use that all the time (and not just bookmarks).  Saving that little bit of vertical space really isn't worth inconvenience.  And when IE 7 first came out, I managed to convince several long time IE users to move to Firefox, in good part because Firefox looks more like a standard Windows app than IE 7 (or IE 8) does.
Anyways, it seems odd to me to try and make Firefox looks more like Chrome or IE8.  If I wanted a browser that looked like IE8 or Chrome, I would use IE8 or Chrome.  Firefox is simply a better browser than either of those two, and should be careful about copying them.

Revision as of 00:22, 28 July 2009

This theme looks beautiful. I have started using Chrome more frequently just for its very clean and light look. I am going to switch to full time use of Firefox as soon as 4 is released. I am hoping to see more screenshots, so that I/we can provide more specific feedback. Do not pay attention to the critics that call this a duplication of Chrome look. This is simple an evolution of a very nice user interface design originally promoted by Google. --Ebegoli 22:12, 27 July 2009 (UTC)

Tabs-on-top: yes or no

Personally i like tabs on top. Right, tabs on top might confuse some users ("Breaks Consistency/Familiarity - Moving things confuses existing users."). I've never developed a Firefox extension or theme (so some of my assumptions might be wrong or already implemented):

1. Implement a mechanism so that every theme supports tabs-on-top and tabs-on-bottom modes (a new requirement for version 4.0 themes to support both modes). Add an option in the preferences pane (default to tabs-on-bottom).

and/or

2. Add an API to write reliable tabs-on-top themes. I know, there's an extension that places tabs on top. But the extension never worked reliably (at least for me): Moving the firefox window does not work when the title-bar is hidden, graphically glitches when used in combination with some themes... I don't know why the tabs-on-top-extension does not work correctly for me. Maybe there's no API to hide the window-title-bar and the extension is using a hack?


--- Tabbed browsing in Chromium is easier to pick up for novice users because of how the URL appears as belonging to each tab. For me it is much more common to see people spawning multiple single tabbed windows with both ie7+ and firefox because of this than in Chromium. This current layout of the user chrome was stablished by Opera waaaaaaay back when there where limited computing resources and ui-controls to choose from, and it should be ditched already. Also, notice that the bookmarks button from A version is missing in B version. --Ponzonik 23:55, 27 July 2009 (UTC)

Progress on tabs instead?

As i stated in the thread about 3.7 and 4.0, why not have the proposed progress indicator on the tabs instead? this makes a lot more sense if you open a new background tab, especially for a new user.


The original post i made:

I noticed the addition of a progressbar under the awesomebar in the 4.0 mockup. Wouldn't it be much better to have progress show on the tabs them selves, that way if i open a lot of tabs at once i can instantly see what tabs are loading and how far along they are. I use tabmixplus for this currently and find it to be a really useful feature.

The progressbar could be a thin one like suggested with the current mockup, or it could be the tab filling with color like the new taskbar in win7 (this way it keeps with the system scheme.)

Just a thought.

--Dipso 23:43, 27 July 2009 (UTC)

There's already a progress indicator and a stronger one would make for a really busy screen. --Ponzonik 23:51, 27 July 2009 (UTC)

I agree with Dipso. Maybe someone can suggest a better idea for how to do it with minimal clutter, but the idea is worth thinking about.

--NoamNelke 00:12, 28 July 2009 (UTC)

Menus

I like the new designs, especially the Chrome-like one (Tabs-on-top), it seems more thought-through (perhaps because Google has).

The part that I liked better about the first (tabs-on-bottom) design is the visual differentiation between controls that relate to the currently visible page (Page menu attached to the top-left corner of it) and controls that relate to the browser (Tools menu right under the close button).

One possible usability issue is that people often don't know in which of the two menus an item is (often happens to me when using Chrome/IE). For that reason (among others) I think it's vital to keep the two menus next to each other (they are on opposite sides of the window in the first design).

Aesthetically, I don't like the way the page menu is attached to the page.

Here's an idea: Look at the second design (tabs-on-top). What if you removed the "tab background" from behind the Tools menu as if the corner of the tab was missing and the menu took up that space. Basically the button would stay where it is now, but it would no longer be on the tab, but on the window behind it.

Here is a Photoshopped image I made to illustrate the idea: Ffidea.png

My idea creates some clutter, so I'm sure someone will come up with a cleaner solution, but I uploaded it anyway to give some food for thought.

--NoamNelke 00:12, 28 July 2009 (UTC)

Is UI change really needed?

Is there really a need to combine the refresh/go/stop buttons? Most people have plenty of horizontal space, and having separate single purpose buttons is a lot less confusing.

Also, why ditch the menu bar? I use that all the time (and not just bookmarks). Saving that little bit of vertical space really isn't worth inconvenience. And when IE 7 first came out, I managed to convince several long time IE users to move to Firefox, in good part because Firefox looks more like a standard Windows app than IE 7 (or IE 8) does.

Anyways, it seems odd to me to try and make Firefox looks more like Chrome or IE8. If I wanted a browser that looked like IE8 or Chrome, I would use IE8 or Chrome. Firefox is simply a better browser than either of those two, and should be careful about copying them.