<?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: Firefox 3 &#8220;find&#8221; UI blunder?</title>
	<atom:link href="http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/</link>
	<description>The 'Net is a waste of time, and that's exactly what's right about it. - William Gibson</description>
	<lastBuildDate>Mon, 22 Feb 2010 06:05:47 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeffrey Zeldman Presents : Saved from the deep</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-882</link>
		<dc:creator>Jeffrey Zeldman Presents : Saved from the deep</dc:creator>
		<pubDate>Wed, 18 Feb 2009 16:15:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-882</guid>
		<description>[...] Firefox 3 ìfindî UI blunder? &#124; David Herrold [...]</description>
		<content:encoded><![CDATA[<p>[...] Firefox 3 ìfindî UI blunder? | David Herrold [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Blandy</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-463</link>
		<dc:creator>Jim Blandy</dc:creator>
		<pubDate>Wed, 13 Aug 2008 20:11:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-463</guid>
		<description>To get completely distracted by a toss-off remark:

Japanese is a confusing case, because both an English-like direction (words left to right, lines top to bottom), and a traditional direction (words top to bottom, lines right to left) are in common use.  So clearly &quot;next&quot; should not be &quot;up&quot;, but just about any other direction would make sense in at least one context.  Most Japanese I&#039;ve seen on the web uses the English-like directions.

Hebrew, on the other hand, does have words going right to left, and lines going down.

Earth-shaking stuff.</description>
		<content:encoded><![CDATA[<p>To get completely distracted by a toss-off remark:</p>
<p>Japanese is a confusing case, because both an English-like direction (words left to right, lines top to bottom), and a traditional direction (words top to bottom, lines right to left) are in common use.  So clearly &#8220;next&#8221; should not be &#8220;up&#8221;, but just about any other direction would make sense in at least one context.  Most Japanese I&#8217;ve seen on the web uses the English-like directions.</p>
<p>Hebrew, on the other hand, does have words going right to left, and lines going down.</p>
<p>Earth-shaking stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cow</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-462</link>
		<dc:creator>Cow</dc:creator>
		<pubDate>Wed, 13 Aug 2008 19:19:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-462</guid>
		<description>I&#039;ve used &quot;Find&quot; a fair bit on Windows and never noticed anything unnatural about the ordering. But I agree it does look odd on the Mac Screenshot you posted: probably because the two buttons are explicitly grouped together with a common border &amp; highlight. Perhaps it would be better to split this into two ungrouped buttons/</description>
		<content:encoded><![CDATA[<p>I&#8217;ve used &#8220;Find&#8221; a fair bit on Windows and never noticed anything unnatural about the ordering. But I agree it does look odd on the Mac Screenshot you posted: probably because the two buttons are explicitly grouped together with a common border &amp; highlight. Perhaps it would be better to split this into two ungrouped buttons/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-431</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Fri, 18 Jul 2008 22:43:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-431</guid>
		<description>Dave, you may be crazy, but this is not evidence of it.  Bill, your response on the other hand doesn&#039;t do you much good.

Previous is to the left, Next is to the right.  Look at, oh say, CD player.

I noticed this mistake on my own and went to see if anyone else found it.  I&#039;ll see if someone beats me to filing a bug.  Considering how bad their UI is in so many places (the &quot;awesome bar&quot; is the &quot;stupid bar&quot;) I&#039;ll bet they close the bug report and say it is perfectly fine.</description>
		<content:encoded><![CDATA[<p>Dave, you may be crazy, but this is not evidence of it.  Bill, your response on the other hand doesn&#8217;t do you much good.</p>
<p>Previous is to the left, Next is to the right.  Look at, oh say, CD player.</p>
<p>I noticed this mistake on my own and went to see if anyone else found it.  I&#8217;ll see if someone beats me to filing a bug.  Considering how bad their UI is in so many places (the &#8220;awesome bar&#8221; is the &#8220;stupid bar&#8221;) I&#8217;ll bet they close the bug report and say it is perfectly fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-403</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Tue, 01 Jul 2008 13:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-403</guid>
		<description>Bill, I agree that the most important button in the find-in-page UI is the &quot;next&quot; button.  This makes sense with regards to &lt;a href=&quot;http://en.wikipedia.org/wiki/Fitts%27s_law&quot; rel=&quot;nofollow&quot;&gt;Fitt&#039;s Law&lt;/a&gt;.  However, we&#039;ve been trained like rats for many years to instinctively look to the right for new things and to the left for old things.

Even our language presents words to us in that order.  However, the &quot;up/down&quot; arrows in the FireFox 2 UI changed that concept. We understand that &quot;new&quot; stuff will be &quot;down&quot; the page, so the down arrow should be first.  That makes sense.

However, when they replaced the arrow icons with rounded buttons they lost the &quot;up/down&quot; concept of the page.  Now we are left with the &quot;left/right&quot; concept to search and that intuitively feels reversed to me.

Or am I crazy?</description>
		<content:encoded><![CDATA[<p>Bill, I agree that the most important button in the find-in-page UI is the &#8220;next&#8221; button.  This makes sense with regards to <a href="http://en.wikipedia.org/wiki/Fitts%27s_law" rel="nofollow">Fitt&#8217;s Law</a>.  However, we&#8217;ve been trained like rats for many years to instinctively look to the right for new things and to the left for old things.</p>
<p>Even our language presents words to us in that order.  However, the &#8220;up/down&#8221; arrows in the FireFox 2 UI changed that concept. We understand that &#8220;new&#8221; stuff will be &#8220;down&#8221; the page, so the down arrow should be first.  That makes sense.</p>
<p>However, when they replaced the arrow icons with rounded buttons they lost the &#8220;up/down&#8221; concept of the page.  Now we are left with the &#8220;left/right&#8221; concept to search and that intuitively feels reversed to me.</p>
<p>Or am I crazy?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Shirley</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-402</link>
		<dc:creator>Bill Shirley</dc:creator>
		<pubDate>Tue, 01 Jul 2008 12:54:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-402</guid>
		<description>After you type something in and search, the next thing you want to do is hit next, so it&#039;s closest to the search field (less to move your mouse).

Previous is like used only very infrequently.

Their relative locations is collectively saving us untold mouse movement a year.  So, I&#039;m with G; I&#039;ll take that bet, Dave.</description>
		<content:encoded><![CDATA[<p>After you type something in and search, the next thing you want to do is hit next, so it&#8217;s closest to the search field (less to move your mouse).</p>
<p>Previous is like used only very infrequently.</p>
<p>Their relative locations is collectively saving us untold mouse movement a year.  So, I&#8217;m with G; I&#8217;ll take that bet, Dave.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-377</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 20 Jun 2008 03:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-377</guid>
		<description>Interesting.  You&#039;re right about the order of the buttons in FF2.  &lt;a href=&quot;http://img.skitch.com/20080620-kn937psdnfa76cmf42xsadp88h.jpg&quot; rel=&quot;nofollow&quot;&gt;I checked the order of the buttons on a PC and they are indeed the same as FF3.&lt;/a&gt;

The notion of UP and DOWN must be more powerful than the odd positioning of the links in FF2.

The connected &quot;next &amp; previous&quot; buttons in FF3 really confused me at first because I instinctively moused over the button on the right without reading the text.

I wonder if they did any user testing on that part of the interface.  I suspect I&#039;m not alone in my mouse confusion.

Or maybe it really IS just me.</description>
		<content:encoded><![CDATA[<p>Interesting.  You&#8217;re right about the order of the buttons in FF2.  <a href="http://img.skitch.com/20080620-kn937psdnfa76cmf42xsadp88h.jpg" rel="nofollow">I checked the order of the buttons on a PC and they are indeed the same as FF3.</a></p>
<p>The notion of UP and DOWN must be more powerful than the odd positioning of the links in FF2.</p>
<p>The connected &#8220;next &#038; previous&#8221; buttons in FF3 really confused me at first because I instinctively moused over the button on the right without reading the text.</p>
<p>I wonder if they did any user testing on that part of the interface.  I suspect I&#8217;m not alone in my mouse confusion.</p>
<p>Or maybe it really IS just me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: G</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-376</link>
		<dc:creator>G</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-376</guid>
		<description>I&#039;ll take that bet.

In Firefox 2 they had that same ordering...the search box, then next, then previous.  The difference is that in Firefox 3, they try to present it as two sides to the same button...a left and a right.  In Firefox 2, they presented it as two buttons with arrows...a down arrow and an up arrow.

Basically, I think they have to keep the order as search box, next, previous. But they need to get the metaphor back to being down and up instead of left and right.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll take that bet.</p>
<p>In Firefox 2 they had that same ordering&#8230;the search box, then next, then previous.  The difference is that in Firefox 3, they try to present it as two sides to the same button&#8230;a left and a right.  In Firefox 2, they presented it as two buttons with arrows&#8230;a down arrow and an up arrow.</p>
<p>Basically, I think they have to keep the order as search box, next, previous. But they need to get the metaphor back to being down and up instead of left and right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-373</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 20 Jun 2008 01:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-373</guid>
		<description>Yeah, I was completely puzzled.  I&#039;m taking bets on whether or not the buttons will be correctly swapped when 3.0.1 is released in the near future.

Any takers?</description>
		<content:encoded><![CDATA[<p>Yeah, I was completely puzzled.  I&#8217;m taking bets on whether or not the buttons will be correctly swapped when 3.0.1 is released in the near future.</p>
<p>Any takers?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://www.davidherrold.com/2008/06/19/firefox-3-find-ui-blunder/comment-page-1/#comment-371</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Fri, 20 Jun 2008 00:45:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidherrold.com/?p=160#comment-371</guid>
		<description>Now that&#039;s a good find. Let&#039;s give them an extreme benefit of the doubt and assume their logic was to put the most frequently used button closer to the text box... at least this way you don&#039;t have to move the mouse *over* the &quot;previous&quot; button which seldom gets used.

For me, I just keep hitting enter to search forward, and shift-enter to search backwards. ~shrug~</description>
		<content:encoded><![CDATA[<p>Now that&#8217;s a good find. Let&#8217;s give them an extreme benefit of the doubt and assume their logic was to put the most frequently used button closer to the text box&#8230; at least this way you don&#8217;t have to move the mouse *over* the &#8220;previous&#8221; button which seldom gets used.</p>
<p>For me, I just keep hitting enter to search forward, and shift-enter to search backwards. ~shrug~</p>
]]></content:encoded>
	</item>
</channel>
</rss>
