<?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"
	>
<channel>
	<title>Comments on: The Shape of Things to Come?</title>
	<atom:link href="http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/</link>
	<description>User Experience Design at Mozilla</description>
	<pubDate>Wed, 08 Oct 2008 00:07:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: t0mpr1c3</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-87540</link>
		<dc:creator>t0mpr1c3</dc:creator>
		<pubDate>Mon, 01 Sep 2008 08:22:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-87540</guid>
		<description>I have reverted to the Firefox 2 theme. Don't like the ugly distracting outsize back button.</description>
		<content:encoded><![CDATA[<p>I have reverted to the Firefox 2 theme. Don&#8217;t like the ugly distracting outsize back button.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Halpin</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-87247</link>
		<dc:creator>John Halpin</dc:creator>
		<pubDate>Sun, 31 Aug 2008 14:05:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-87247</guid>
		<description>I for one much preferred the old Firefox buttons. The new ones with their plastic look, chunky feel, irregular size and over saturated colours call too much attention away from what I want to look at ie. the page content.</description>
		<content:encoded><![CDATA[<p>I for one much preferred the old Firefox buttons. The new ones with their plastic look, chunky feel, irregular size and over saturated colours call too much attention away from what I want to look at ie. the page content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-77873</link>
		<dc:creator>michael</dc:creator>
		<pubDate>Sun, 27 Jul 2008 18:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-77873</guid>
		<description>The back button is WRONG. It is just plain wrong. I am thinking of rolling back to 2 for that one reason alone. It is so distracting and unbalanced. It's like a zen garden with a car wreck on the path.</description>
		<content:encoded><![CDATA[<p>The back button is WRONG. It is just plain wrong. I am thinking of rolling back to 2 for that one reason alone. It is so distracting and unbalanced. It&#8217;s like a zen garden with a car wreck on the path.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bamm Gabriana</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-44838</link>
		<dc:creator>Bamm Gabriana</dc:creator>
		<pubDate>Mon, 31 Mar 2008 15:31:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-44838</guid>
		<description>Unfortunately, you should not equate

Linux Users == Gnome Users

I for one am a KDE user, and I believe I am not the only KDE user who is also a Firefox user.

I would rather have the keyhole back button in Linux than Gnome integration. The same code that makes Firefox look great in Gnome also makes it look horrible in KDE.

My suggestion: a KDE-specific theme. The Keyhole with a large Back button would look perfect with the new "Oxygen" look and feel.

If you are willing to start a project for the KDE-specific theme, then I'm willing to join the team! I had some Firefox theming experience in the past when I made an Internet Explorer theme, so I know that little details mean a lot to make the theme enjoyable to use.

Just let me know if my help is needed, and how I can help.</description>
		<content:encoded><![CDATA[<p>Unfortunately, you should not equate</p>
<p>Linux Users == Gnome Users</p>
<p>I for one am a KDE user, and I believe I am not the only KDE user who is also a Firefox user.</p>
<p>I would rather have the keyhole back button in Linux than Gnome integration. The same code that makes Firefox look great in Gnome also makes it look horrible in KDE.</p>
<p>My suggestion: a KDE-specific theme. The Keyhole with a large Back button would look perfect with the new &#8220;Oxygen&#8221; look and feel.</p>
<p>If you are willing to start a project for the KDE-specific theme, then I&#8217;m willing to join the team! I had some Firefox theming experience in the past when I made an Internet Explorer theme, so I know that little details mean a lot to make the theme enjoyable to use.</p>
<p>Just let me know if my help is needed, and how I can help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Silver</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-35388</link>
		<dc:creator>Kris Silver</dc:creator>
		<pubDate>Sat, 16 Feb 2008 15:05:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-35388</guid>
		<description>Very impressed with this write up, the work being done, and the beta 3 theme overall.  A couple of improvements:

1. The back/forwards drop-down - Placed right of forwards suggests its only for forwards, and is less recognizable as an arrow.  The history icon between the two is far more intuitive and I hope this ends as the final design in Fx3.

2. New tab button - not overly recognizable, looks too much like a window.  Also, with tabs being default, isn't it about time this simplest function for this default behavior, gets a button in the default interface?

3. Search drop-down - I'd like to see Fx follow native visual design and icons for search. Currently the tiny drop-down icon on the engine itself is not overly native, recognizable or intuitive.  

A proper drop-down icon to the right of the search bar (where per location bar users expect drop-down buttons) would be far more native and intuitive.  Not only would this be more consistent with Os's, and other browsers such as Opera and IE7, it opens up other development area's.  These include find in page more easily accessible via the drop-down as an all round search drop-down, per other browsers and programs.  Not to mention find more engines as an more accessible option in the drop-down.</description>
		<content:encoded><![CDATA[<p>Very impressed with this write up, the work being done, and the beta 3 theme overall.  A couple of improvements:</p>
<p>1. The back/forwards drop-down - Placed right of forwards suggests its only for forwards, and is less recognizable as an arrow.  The history icon between the two is far more intuitive and I hope this ends as the final design in Fx3.</p>
<p>2. New tab button - not overly recognizable, looks too much like a window.  Also, with tabs being default, isn&#8217;t it about time this simplest function for this default behavior, gets a button in the default interface?</p>
<p>3. Search drop-down - I&#8217;d like to see Fx follow native visual design and icons for search. Currently the tiny drop-down icon on the engine itself is not overly native, recognizable or intuitive.  </p>
<p>A proper drop-down icon to the right of the search bar (where per location bar users expect drop-down buttons) would be far more native and intuitive.  Not only would this be more consistent with Os&#8217;s, and other browsers such as Opera and IE7, it opens up other development area&#8217;s.  These include find in page more easily accessible via the drop-down as an all round search drop-down, per other browsers and programs.  Not to mention find more engines as an more accessible option in the drop-down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Churchill</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-35314</link>
		<dc:creator>Steve Churchill</dc:creator>
		<pubDate>Sat, 16 Feb 2008 07:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-35314</guid>
		<description>I like the new features and believe 3.0 is much faster, however, I'd prefer the old bookmark features that allowed the user to completely personalize it.</description>
		<content:encoded><![CDATA[<p>I like the new features and believe 3.0 is much faster, however, I&#8217;d prefer the old bookmark features that allowed the user to completely personalize it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Magumi</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-35136</link>
		<dc:creator>Magumi</dc:creator>
		<pubDate>Fri, 15 Feb 2008 14:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-35136</guid>
		<description>I agree that the history button looks out of place between the back and forward buttons. I also don't see the point of making the start of both the address and search fields rounded on Windows. Either make both ends square or just make the start of the first and the end of the second rounded.</description>
		<content:encoded><![CDATA[<p>I agree that the history button looks out of place between the back and forward buttons. I also don&#8217;t see the point of making the start of both the address and search fields rounded on Windows. Either make both ends square or just make the start of the first and the end of the second rounded.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-35030</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 15 Feb 2008 06:08:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-35030</guid>
		<description>I absolutely cannot believe you left that fucking hideous, huge back button in there. 

I love Firefox, but I will never, ever use FF3 with that travesty of wasting my motherfucking screen real estate in there.</description>
		<content:encoded><![CDATA[<p>I absolutely cannot believe you left that fucking hideous, huge back button in there. </p>
<p>I love Firefox, but I will never, ever use FF3 with that travesty of wasting my motherfucking screen real estate in there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-34640</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 13 Feb 2008 10:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-34640</guid>
		<description>I'm sorry, but... it's ugly. Like, really ugly.

Please change it? Please? Please please please?

Or you'll see half of the people walk past my desk going.. wow, that's ugly, what's that?

Oh, it's Firefox.

Yeah, IE looks better.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry, but&#8230; it&#8217;s ugly. Like, really ugly.</p>
<p>Please change it? Please? Please please please?</p>
<p>Or you&#8217;ll see half of the people walk past my desk going.. wow, that&#8217;s ugly, what&#8217;s that?</p>
<p>Oh, it&#8217;s Firefox.</p>
<p>Yeah, IE looks better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Harkless</title>
		<link>http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-30597</link>
		<dc:creator>Dan Harkless</dc:creator>
		<pubDate>Fri, 25 Jan 2008 02:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/2007/11/15/the-shape-of-things-to-come/#comment-30597</guid>
		<description>Argh, would be nice if your blog software had a Preview button for comments and/or took the common approach of not including trailing commas or periods when auto-hyperlinking an apparent URL.  Here's the URL I gave again without the period at the end of the sentence: http://test.johnath.com/dropzone/Beyond%20the%20Padlock%20v7.pdf</description>
		<content:encoded><![CDATA[<p>Argh, would be nice if your blog software had a Preview button for comments and/or took the common approach of not including trailing commas or periods when auto-hyperlinking an apparent URL.  Here&#8217;s the URL I gave again without the period at the end of the sentence: <a href="http://test.johnath.com/dropzone/Beyond%20the%20Padlock%20v7.pdf" rel="nofollow">http://test.johnath.com/dropzone/Beyond%20the%20Padlock%20v7.pdf</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
