FX2 Visual Update/User Interface Design: Difference between revisions

← Older edit

FX2 Visual Update/User Interface Design (view source)

Revision as of 21:24, 5 May 2006

5,686 bytes added , 5 May 2006

no edit summary

Ge.diego

82

edits

@@ Line 1: / Line 1: @@
-There is a proposal to modify the default chrome presentation in Firefox 2. It's currently [http://groups.google.com/group/mozilla.dev.apps.firefox/browse_frm/thread/85a8c60c5b9a3f93/94c5001eac7c503a?tvc=1#94c5001eac7c503a being discussed in the newsgroup].
+There is a proposal to modify the default chrome presentation in Firefox 2. It's currently being discussed in the [http://groups.google.com/group/mozilla.dev.apps.firefox/browse_frm/thread/6947a05fed1e088c/73c66a86dd3cf11d#73c66a86dd3cf11d newsgroup].
+[[User:Ge.diego|Ge.diego]] made some [[User:Ge.diego/Tab_Management_Comments|comments on Ben Godger test build that includes new tab management]] and gave an [[User:Ge.diego/User_Interface_Mockup|alternative user interface mockup proposal]].
+= Roundup & Decisions =
+<pre><nowiki>
+ New Mockup:
+                         (2)                                    (5) -.
+             (1)          |        (3)-.----.           (4) -.       |
+              |           v            v    v                v       v
+ .----------------------------------------------------------------------.
+ | File   Edit   View   History   Bookmarks   Tools   Help     [_][=][x]|
+ |----------------------------------------------------------------------|
+ |.--. .--. .--.  ,-------------------..--,,-,   ,----------.---,,  .i. |
+ ||<-| |->| |[]| ( {} www.foo.com   v ||.)||=>) (  google G |.O |)  -O- |
+ |'--' '--' '--'  `-------------------''--''-'   '----------'--v''  'i' |
+ |----------------------------------------------------------------------|
+ |(.O) (&) (BBC News v) (Mozilla)                                       |
+ |.-----------,.-----------,.-----------,-------------------------------|
+ ||{} Bar     || {} Foo (x)|| {} Baz    |                               |
+ |-------------'           '--------------------------------------------|
+ |                                                                    |^|
+ |                                                                    |H|
+ :                             (page content)                         : :
+ .                                                                    . .
+ :                                                                    : :
+ |                                                                    |V|
+ |                                                                    //|
+ '----------------------------------------------------------------------'
+ | New tab: http://www.foobarbaz.com                                    |
+ '----------------------------------------------------------------------'
+  ^     ^                ^       ^                             ^
+  '     |                |       |                             |
+  (6)   '- (7)      (8) -'       '- (9)                  (10) -'
+</nowiki></pre>
+Summary of feedback and decisions:
+(1) It was noted that "Stop" needs to be a large, easy to find button that people can quickly click in order to stop page loading, and that often the button is used to stop AJAX and script-y things that keep loading resources even after the page is loaded. Also, see (3) for discussion on the stateful Stop/Go button.
+(2) Renaming "Go" menu to "History" was seen as a good idea.
+(3) Putting buttons inside the URL bar led to interesting questions about how they could be taken out again. Any such system would require a lot of work and make the UI more complex. Instead, it will be safer/easier to allow buttons to be "docked" to the edge toolbar, and keep the space inside the URL bar for indicators (which will still be made to look like buttons to lend a button-like affordance)
+Combining the Go/Stop button was seen as interesting, but potentially dangerous and confusing. It occurred to some that a more natural optimization would be to combine the Go and Reload functions, since when a page is loading or loaded, the functions are equivalent. The behaviour would be:
+* When URL field is being modified   == button is "Go"
+* Page is loading                    == button is "Go"
+* Page has loaded                    == button is "Refresh"
+(4) Putting the search engine selector at the right (left for Mac) and using grey text in the background was seen as a good idea.
+(5) Using the throbber as a progress indicator was seen as a good idea, and should be enabled both in the upper-right corner and on tabs.
+(6) Putting the "Search Bookmarks" button on the Bookmark Toolbar was seen as a good idea, as long as it could be moved back to the Toolbar.
+(7) Moving the "Home" button to the Bookmark Toolbar was contentious, and users should be allowed to move it back to the main toolbar.
+(8) Close buttons on the active tab only was seen as the best strategy to improve the usability of a "close single tab" task while also preserving tab strip real estate. Exposing background close of tabs wasn't seen as an important enough case to show them on all tabs. A "Close Tab" button should also be added to the "Customize" palette.
+(9) Optimizing tab width to support a consistent (X) location for quickly closing multiple tabs wasn't seen as being worth the cost of reducing the space available for having multiple tabs open before hitting tab overflow solutions. Some good alternatives were proposed the best being that tabs shrink as they are opened, and stay at the same width when closed with the mouse *until* the user moves the cursor away from the tabstrip, at which point they subtly stretch to fit the available space.
+(10) Hiding the status bar by default was very contentious. People expressed concern at not being to see the link destinations, as well
+as the browser "feeling" slower when the user can't see the messages about contacting the remote server, etc. It should be left on. The text in the statusbar should indicate if a link will be opened in a new window (Opens new window: ...), a new tab (Opens new tab: ...), or replace content (Go to: ...)
+Discussion question consensuses ..:
+(A) Keep the Bookmark Toolbar
+(B) Use the post-it note metaphor for indicating that a page has tags
+(C) (This functionality will be part of Places anyway)
+(D) (We're keeping the status bar, this discussion is moot)
+(E) Changing the mouse cursor was seen as a good idea
 = Initial Proposal =
@@ Line 13: / Line 84: @@
   |.--. .--.  ,.--.-------------------.--,,--,.   ,----------.---,,  .i. |
   ||<-| |->| ( |^v| {} www.foo.com  v |.)||=>| ) (  google G |.O |)  -O- |
-  |'--' '--'  `'--'-------------------'--''--''   '----------'--v''  'i' |
+  |'--' '--'  `'--'-------------------'--'`--`'   '----------'--v`'  'i' |
   |----------------------------------------------------------------------|
   |(.O) (&) (BBC News v) (Mozilla)                                       |