<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: No Ribbon Planned for the Firefox UI</title>
	<atom:link href="http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/</link>
	<description>User Experience Design at Mozilla</description>
	<lastBuildDate>Sun, 12 Feb 2012 23:42:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Funny Love Quotes</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-165698</link>
		<dc:creator>Funny Love Quotes</dc:creator>
		<pubDate>Fri, 31 Dec 2010 10:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-165698</guid>
		<description>I think more than merely thinking about the UI (which can be solved to some extend by themes) think about the memory management. I personally have a problem, with firefox not releasing it&#039;s memory.</description>
		<content:encoded><![CDATA[<p>I think more than merely thinking about the UI (which can be solved to some extend by themes) think about the memory management. I personally have a problem, with firefox not releasing it&#8217;s memory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Soft Where</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-159554</link>
		<dc:creator>Soft Where</dc:creator>
		<pubDate>Wed, 14 Jul 2010 23:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-159554</guid>
		<description>&quot;Invent&quot; all you want but PRESERVE existing familiarity, PRESERVE existing look and feel, PRESERVE the classic UI etc. What is up with the arrogance of software companies and &quot;developers&quot; throwing away 10+ years of UI familiarity just so they can &quot;invent&quot; something new with just the right shade of baby-blue and screen-wasting fat toolbars (ie. ribbon). I say: learn about usability and UI options please. When designing a user interface PRESERVE existing designs and make the UI fully customizable. UI 101.</description>
		<content:encoded><![CDATA[<p>&#8220;Invent&#8221; all you want but PRESERVE existing familiarity, PRESERVE existing look and feel, PRESERVE the classic UI etc. What is up with the arrogance of software companies and &#8220;developers&#8221; throwing away 10+ years of UI familiarity just so they can &#8220;invent&#8221; something new with just the right shade of baby-blue and screen-wasting fat toolbars (ie. ribbon). I say: learn about usability and UI options please. When designing a user interface PRESERVE existing designs and make the UI fully customizable. UI 101.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jocco</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-159414</link>
		<dc:creator>jocco</dc:creator>
		<pubDate>Thu, 08 Jul 2010 01:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-159414</guid>
		<description>I would like be able to move all menus and tools to the right click context menu.</description>
		<content:encoded><![CDATA[<p>I would like be able to move all menus and tools to the right click context menu.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Noble</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-158003</link>
		<dc:creator>Sean Noble</dc:creator>
		<pubDate>Tue, 11 May 2010 15:20:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-158003</guid>
		<description>As long as the new right-side menu items and other UI elements can be easily accessed using Alt- keyboard shortcuts, all will be well :)

Of course not having a ribbon is fine - wise choice.  A ribbon is correct when there is a large variety of tools that need to be regularly accessed.  This is not the case for web browsers.

Good work -S</description>
		<content:encoded><![CDATA[<p>As long as the new right-side menu items and other UI elements can be easily accessed using Alt- keyboard shortcuts, all will be well :)</p>
<p>Of course not having a ribbon is fine &#8211; wise choice.  A ribbon is correct when there is a large variety of tools that need to be regularly accessed.  This is not the case for web browsers.</p>
<p>Good work -S</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-157773</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Sun, 02 May 2010 07:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-157773</guid>
		<description>Expanding my post at 45. In Word most of the time you use the ribbons to format text and layout the document. you use a browser to go from web site to site. Turning the bookmarks toolbar into multiple ribbons is absolutely natural for a browser.

If Microsoft get there first I think they will get back a big chunk of the market. To me this is the next big thing in browsers.</description>
		<content:encoded><![CDATA[<p>Expanding my post at 45. In Word most of the time you use the ribbons to format text and layout the document. you use a browser to go from web site to site. Turning the bookmarks toolbar into multiple ribbons is absolutely natural for a browser.</p>
<p>If Microsoft get there first I think they will get back a big chunk of the market. To me this is the next big thing in browsers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-157772</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Sun, 02 May 2010 07:42:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-157772</guid>
		<description>The plans for a ribbon interface miss the point. The settings and options in Firefox are hardly ever changed. What I want is an Office 2010 style ribbons made up of WEB SITES.
The Backstage and About areas can be used for all Firefox settings. I want to set up menus like News, Finance, Shopping, Food etc.. Each ribbon would be customisable (like Office 2010). There would be sections with web site icons and optional names. I think this would be a Very big win for Firefox. Maybe ribbon view could be an option or extension.

Hiding the menu bar like FX4 is a very bad idea. The developers need to be realistic about users. Do you really think a 6 year old or a 90 year old is going to know about or understand Alt?

My other big gripe about Firefox is everything is too small on a 1920 x 1080 monitor. It looks terrible. I eventually found the about:config parameter layout.css.devPixelsPerPx which works like magic. This option should be on a menu. Again this is probably a case of young developers with good eyesight not understanding some of their users.</description>
		<content:encoded><![CDATA[<p>The plans for a ribbon interface miss the point. The settings and options in Firefox are hardly ever changed. What I want is an Office 2010 style ribbons made up of WEB SITES.<br />
The Backstage and About areas can be used for all Firefox settings. I want to set up menus like News, Finance, Shopping, Food etc.. Each ribbon would be customisable (like Office 2010). There would be sections with web site icons and optional names. I think this would be a Very big win for Firefox. Maybe ribbon view could be an option or extension.</p>
<p>Hiding the menu bar like FX4 is a very bad idea. The developers need to be realistic about users. Do you really think a 6 year old or a 90 year old is going to know about or understand Alt?</p>
<p>My other big gripe about Firefox is everything is too small on a 1920 x 1080 monitor. It looks terrible. I eventually found the about:config parameter layout.css.devPixelsPerPx which works like magic. This option should be on a menu. Again this is probably a case of young developers with good eyesight not understanding some of their users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stacy Sherrill</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-155516</link>
		<dc:creator>Stacy Sherrill</dc:creator>
		<pubDate>Sat, 06 Mar 2010 14:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-155516</guid>
		<description>Alex, if I may quote a most excellent previous blog post of yours, &quot;Notifications and Flow&quot; of March 24, 2009, 

&lt;b&gt;&quot;When designing interfaces we often tend to focus on aspects like discoverability and functionality. For instance, if we didn’t place the Web feed glyph in the location bar, how would users be able to discover that they could subscribe to pages?&lt;/b&gt;

Indeed!  But what you seem to be suggesting is doing away with discoverability, or at least making it more difficult.  Certainly this will not impact the FF user already experienced on the new GUI, but it will impact new users to that particular design and to FF in general.  

Do you really want to make their &#039;introduction&#039; to a new way of surfing difficult. 

In that same article, you discussed as a primary mime the breaking of cognitive flow when attempting to help the user.  Unless you are very careful this next design, I think you are going to prevent cognition in the first place. 

P.S.  Love your work.  You should write more often.</description>
		<content:encoded><![CDATA[<p>Alex, if I may quote a most excellent previous blog post of yours, &#8220;Notifications and Flow&#8221; of March 24, 2009, </p>
<p><b>&#8220;When designing interfaces we often tend to focus on aspects like discoverability and functionality. For instance, if we didn’t place the Web feed glyph in the location bar, how would users be able to discover that they could subscribe to pages?</b></p>
<p>Indeed!  But what you seem to be suggesting is doing away with discoverability, or at least making it more difficult.  Certainly this will not impact the FF user already experienced on the new GUI, but it will impact new users to that particular design and to FF in general.  </p>
<p>Do you really want to make their &#8216;introduction&#8217; to a new way of surfing difficult. </p>
<p>In that same article, you discussed as a primary mime the breaking of cognitive flow when attempting to help the user.  Unless you are very careful this next design, I think you are going to prevent cognition in the first place. </p>
<p>P.S.  Love your work.  You should write more often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elmario</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-155255</link>
		<dc:creator>Elmario</dc:creator>
		<pubDate>Mon, 01 Mar 2010 14:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-155255</guid>
		<description>I dont&#039; really get, what&#039;s up with these GUI Designers! Every of this new and sooo &#039;innovative&#039; GUIs (Office 2007, Windows Vista, Windows 7, Firefox 4.0) tries to be an apple like piece of designershit, givin the look of it 100% priority, while flushing usability down the toilet. WTF? If they continue doing this, I&#039;ll not bee using computers anymore in future - and I&#039;m not what I would call an unexperienced person :(</description>
		<content:encoded><![CDATA[<p>I dont&#8217; really get, what&#8217;s up with these GUI Designers! Every of this new and sooo &#8216;innovative&#8217; GUIs (Office 2007, Windows Vista, Windows 7, Firefox 4.0) tries to be an apple like piece of designershit, givin the look of it 100% priority, while flushing usability down the toilet. WTF? If they continue doing this, I&#8217;ll not bee using computers anymore in future &#8211; and I&#8217;m not what I would call an unexperienced person :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex.r.</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-151732</link>
		<dc:creator>alex.r.</dc:creator>
		<pubDate>Thu, 10 Dec 2009 21:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-151732</guid>
		<description>The problem I have with using these two buttons instead of the menu is that their wording is too generic to be useful and they require too much thought from the user to be useful.

Say I want to print the current page. Well, my printer is some kind of tool I guess, so it might be under there. But it&#039;s also the current page that I want to print, so it might be over there... 

And printing is just an example, any action not in the toolbar would require some pause and thought -- and since these are things I do once in a fortnight on a browser, you can&#039;t really rely on muscle memory to guide me there.

Hence the consistency with the other applications for which I do print, copy/cut/paste more often is nice, because I can benefit from the muscle memory gathered there and use it on the browser.</description>
		<content:encoded><![CDATA[<p>The problem I have with using these two buttons instead of the menu is that their wording is too generic to be useful and they require too much thought from the user to be useful.</p>
<p>Say I want to print the current page. Well, my printer is some kind of tool I guess, so it might be under there. But it&#8217;s also the current page that I want to print, so it might be over there&#8230; </p>
<p>And printing is just an example, any action not in the toolbar would require some pause and thought &#8212; and since these are things I do once in a fortnight on a browser, you can&#8217;t really rely on muscle memory to guide me there.</p>
<p>Hence the consistency with the other applications for which I do print, copy/cut/paste more often is nice, because I can benefit from the muscle memory gathered there and use it on the browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: netrunner</title>
		<link>http://blog.mozilla.com/faaborg/2009/09/24/no-ribbon-planned-for-the-firefox-ui/comment-page-1/#comment-151688</link>
		<dc:creator>netrunner</dc:creator>
		<pubDate>Wed, 09 Dec 2009 21:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=232#comment-151688</guid>
		<description>I gotta say I love the odd selective memory people have for the loss of a menu bar. This happened in IE7 first (down to the &quot;Tools,&quot; &quot;Page&quot; buttons), friends, not Chrome.

This has been a long time coming, as has the integration of search bar with address bar. However, Eevee&#039;s comments (#9) are apt - please think carefully about how you are going to arrange/drop the functionality that used to hide in those poorly-designed menus.

Finally, the problem of discoverability (http://people.mozilla.com/~faaborg/files/20091012-personalWeb/UnifyingSearch_i2.png) is still around. This will be less of a problem once the search engine box is integrated, thus forcing people to treat it as a place to do searching, but that&#039;s not quite enough. For example, when using Chrome I usually tune out all but the web results.</description>
		<content:encoded><![CDATA[<p>I gotta say I love the odd selective memory people have for the loss of a menu bar. This happened in IE7 first (down to the &#8220;Tools,&#8221; &#8220;Page&#8221; buttons), friends, not Chrome.</p>
<p>This has been a long time coming, as has the integration of search bar with address bar. However, Eevee&#8217;s comments (#9) are apt &#8211; please think carefully about how you are going to arrange/drop the functionality that used to hide in those poorly-designed menus.</p>
<p>Finally, the problem of discoverability (<a href="http://people.mozilla.com/~faaborg/files/20091012-personalWeb/UnifyingSearch_i2.png" rel="nofollow">http://people.mozilla.com/~faaborg/files/20091012-personalWeb/UnifyingSearch_i2.png</a>) is still around. This will be less of a problem once the search engine box is integrated, thus forcing people to treat it as a place to do searching, but that&#8217;s not quite enough. For example, when using Chrome I usually tune out all but the web results.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

