<?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: Recreating the button</title>
	<atom:link href="http://stopdesign.com/archive/2009/02/04/recreating-the-button.html/feed" rel="self" type="application/rss+xml" />
	<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html</link>
	<description>Stopdesign is the creative outlet of Douglas Bowman.</description>
	<lastBuildDate>Tue, 04 May 2010 11:39:03 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Glenn</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4409</link>
		<dc:creator>Glenn</dc:creator>
		<pubDate>Tue, 10 Feb 2009 13:39:19 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4409</guid>
		<description>@Doug: The new buttons look well enough, but the hover effect is so subtle as to be almost invisible; I look forward to them being skin-able (in userChrome, Stylish--I&#039;d like some color variations). All in all, the more I use it (the new button design), the more I like it (some things take more time getting used to than others). Love the Planets, too--more images would be nice though. Thanks.

@Kristin: If you think the &quot;Move to&quot; and &quot;Labels&quot; buttons are redundant, then you haven&#039;t used them. One adds a label; the other adds a label and removes a label, effectively &quot;moving&quot; a message--actually a real time-saver (for me at least).</description>
		<content:encoded><![CDATA[<p>@Doug: The new buttons look well enough, but the hover effect is so subtle as to be almost invisible; I look forward to them being skin-able (in userChrome, Stylish&#8211;I&#8217;d like some color variations). All in all, the more I use it (the new button design), the more I like it (some things take more time getting used to than others). Love the Planets, too&#8211;more images would be nice though. Thanks.</p>
<p>@Kristin: If you think the &#8220;Move to&#8221; and &#8220;Labels&#8221; buttons are redundant, then you haven&#8217;t used them. One adds a label; the other adds a label and removes a label, effectively &#8220;moving&#8221; a message&#8211;actually a real time-saver (for me at least).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4405</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Sat, 07 Feb 2009 00:44:19 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4405</guid>
		<description>Doug, thanks a lot for the explanation.  I took your advice, and spent some time reverse-engineering the buttons on Gmail.

I also wrote about how I created &lt;a href=&quot;http://blog.kaeding.name/articles/2009/02/06/gmail-style-buttons-with-no-images&quot; rel=&quot;nofollow&quot;&gt;Gmail-style buttons with no images&lt;/a&gt; on my blog, if anyone is interested.</description>
		<content:encoded><![CDATA[<p>Doug, thanks a lot for the explanation.  I took your advice, and spent some time reverse-engineering the buttons on Gmail.</p>
<p>I also wrote about how I created <a href="http://blog.kaeding.name/articles/2009/02/06/gmail-style-buttons-with-no-images" rel="nofollow">Gmail-style buttons with no images</a> on my blog, if anyone is interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luc</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4404</link>
		<dc:creator>Luc</dc:creator>
		<pubDate>Fri, 06 Feb 2009 22:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4404</guid>
		<description>Doug, thanks for the great post. I love this kind of insight. When I saw those buttons in gmail, I immediatly thought you were the one responsible for the design work and css coding. I guess I was not mistaken!</description>
		<content:encoded><![CDATA[<p>Doug, thanks for the great post. I love this kind of insight. When I saw those buttons in gmail, I immediatly thought you were the one responsible for the design work and css coding. I guess I was not mistaken!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Benton</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4403</link>
		<dc:creator>Jim Benton</dc:creator>
		<pubDate>Fri, 06 Feb 2009 22:36:19 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4403</guid>
		<description>Great article. I&#039;ve been dealing with the issues of using &lt;code&gt;button&lt;/code&gt; elements for a while now, and I almost always end up using an approach similar to the one presented here (a button with several nested spans).

Another way to deal with the annoying extra padding Firefox adds to buttons is:

&lt;code&gt;button::-moz-focus-inner{padding:0;border:none}&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Great article. I&#8217;ve been dealing with the issues of using <code>button</code> elements for a while now, and I almost always end up using an approach similar to the one presented here (a button with several nested spans).</p>
<p>Another way to deal with the annoying extra padding Firefox adds to buttons is:</p>
<p><code>button::-moz-focus-inner{padding:0;border:none}</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby Ho</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4402</link>
		<dc:creator>Toby Ho</dc:creator>
		<pubDate>Fri, 06 Feb 2009 20:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4402</guid>
		<description>I love this! I was looking at the new buttons with firebug and was pleasantly surprised, which lead me here. This buttons look great and it would surely save me the trouble of making all those image buttons.</description>
		<content:encoded><![CDATA[<p>I love this! I was looking at the new buttons with firebug and was pleasantly surprised, which lead me here. This buttons look great and it would surely save me the trouble of making all those image buttons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor Noagbodji</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4401</link>
		<dc:creator>Victor Noagbodji</dc:creator>
		<pubDate>Fri, 06 Feb 2009 18:39:17 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4401</guid>
		<description>I also wanted to investigate these new buttons as they stroke my designer&#039;s pride (well, I actually inspected them with Chrome =]). Great to see the explanations here. Thanks a lot.</description>
		<content:encoded><![CDATA[<p>I also wanted to investigate these new buttons as they stroke my designer&#8217;s pride (well, I actually inspected them with Chrome =]). Great to see the explanations here. Thanks a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Jehl</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4400</link>
		<dc:creator>Scott Jehl</dc:creator>
		<pubDate>Fri, 06 Feb 2009 18:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4400</guid>
		<description>@Douglas Bowman: Sorry for the confusion. I wrongly assumed the end-implementation was the same as your demo code. I suppose my question should instead be directed at Google ;)</description>
		<content:encoded><![CDATA[<p>@Douglas Bowman: Sorry for the confusion. I wrongly assumed the end-implementation was the same as your demo code. I suppose my question should instead be directed at Google ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Bowman</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4399</link>
		<dc:creator>Douglas Bowman</dc:creator>
		<pubDate>Fri, 06 Feb 2009 18:07:43 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4399</guid>
		<description>&lt;a href=&quot;#comment-4438&quot; rel=&quot;nofollow&quot;&gt;@Amy&lt;/a&gt; - That tripped me up too at first. I think you&#039;re asking about why the menu items in the drop down don&#039;t have any rollover state change? If so, it&#039;s because you don&#039;t have any messages/threads selected, so none of the actions in the More actions drop down are selectable. Select a message, and instantly everything in that menu comes to life (and changes by context of what you&#039;ve selected too).</description>
		<content:encoded><![CDATA[<p><a href="#comment-4438" rel="nofollow">@Amy</a> &#8211; That tripped me up too at first. I think you&#8217;re asking about why the menu items in the drop down don&#8217;t have any rollover state change? If so, it&#8217;s because you don&#8217;t have any messages/threads selected, so none of the actions in the More actions drop down are selectable. Select a message, and instantly everything in that menu comes to life (and changes by context of what you&#8217;ve selected too).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Jehl</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4398</link>
		<dc:creator>Scott Jehl</dc:creator>
		<pubDate>Fri, 06 Feb 2009 18:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4398</guid>
		<description>That said, I like your demo pages with button elements much more. :)
Was mainly referring the gmail implementation...</description>
		<content:encoded><![CDATA[<p>That said, I like your demo pages with button elements much more. :)<br />
Was mainly referring the gmail implementation&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Bowman</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4397</link>
		<dc:creator>Douglas Bowman</dc:creator>
		<pubDate>Fri, 06 Feb 2009 18:01:55 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4397</guid>
		<description>&lt;a href=&quot;#comment-4454&quot; rel=&quot;nofollow&quot;&gt;@Scott Jehl&lt;/a&gt; - Nice examples using jQuery. Curious if you&#039;re asking about the markup that made it live in production (not my code) and was &lt;a href=&quot;#comment-4389&quot; rel=&quot;nofollow&quot;&gt;posted by Ozan&lt;/a&gt; above? Or if you&#039;re asking about the markup in either of the two demos I linked in the entry?</description>
		<content:encoded><![CDATA[<p><a href="#comment-4454" rel="nofollow">@Scott Jehl</a> &#8211; Nice examples using jQuery. Curious if you&#8217;re asking about the markup that made it live in production (not my code) and was <a href="#comment-4389" rel="nofollow">posted by Ozan</a> above? Or if you&#8217;re asking about the markup in either of the two demos I linked in the entry?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Jehl</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4396</link>
		<dc:creator>Scott Jehl</dc:creator>
		<pubDate>Fri, 06 Feb 2009 17:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4396</guid>
		<description>This is an interesting experiment, though I have to say it seems to be more of a CSS feat than a practical solution in an accessible web app. As others have noted, using a div seems odd, even if does render faster. I&#039;m curious: if divs were chosen in the name of performance, did Google find that using several nested divs per button was still more performant than a single focusable/accessible anchor? Using an anchor would at least afford native key access across browsers; did they find a way around that problem?

I feel silly saying all this, given your status as a godfather of web design and all :). But I think the implications of the markup you&#039;ve shown are worth discussing.

Just as food for thought... we&#039;ve done quite a lot of work with styling button elements and have written of our findings over in our process lab/blog. The end result of our work is built into the new jQuery UI CSS Framework. It does use images (one per state), but only one element (anchor or button), and provides an array of icon choices and textures to to choose from. It might not have fit the parameters Google was shooting for, but I think it&#039;s relevant to the discussion to present an alternate approach. http://www.filamentgroup.com/lab/styling_buttons_and_toolbars_with_the_jquery_ui_css_framework/</description>
		<content:encoded><![CDATA[<p>This is an interesting experiment, though I have to say it seems to be more of a CSS feat than a practical solution in an accessible web app. As others have noted, using a div seems odd, even if does render faster. I&#8217;m curious: if divs were chosen in the name of performance, did Google find that using several nested divs per button was still more performant than a single focusable/accessible anchor? Using an anchor would at least afford native key access across browsers; did they find a way around that problem?</p>
<p>I feel silly saying all this, given your status as a godfather of web design and all :). But I think the implications of the markup you&#8217;ve shown are worth discussing.</p>
<p>Just as food for thought&#8230; we&#8217;ve done quite a lot of work with styling button elements and have written of our findings over in our process lab/blog. The end result of our work is built into the new jQuery UI CSS Framework. It does use images (one per state), but only one element (anchor or button), and provides an array of icon choices and textures to to choose from. It might not have fit the parameters Google was shooting for, but I think it&#8217;s relevant to the discussion to present an alternate approach. <a href="http://www.filamentgroup.com/lab/styling_buttons_and_toolbars_with_the_jquery_ui_css_framework/" rel="nofollow">http://www.filamentgroup.com/lab/styling_buttons_and_toolbars_with_the_jquery_ui_css_framework/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tommy</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4395</link>
		<dc:creator>Tommy</dc:creator>
		<pubDate>Fri, 06 Feb 2009 15:53:15 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4395</guid>
		<description>Hey Doug,

Did you all work with the elusive file form element (for uploading files) and it&#039;s hard to style button at all?</description>
		<content:encoded><![CDATA[<p>Hey Doug,</p>
<p>Did you all work with the elusive file form element (for uploading files) and it&#8217;s hard to style button at all?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Bristow</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4394</link>
		<dc:creator>Alan Bristow</dc:creator>
		<pubDate>Fri, 06 Feb 2009 14:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4394</guid>
		<description>THANK you for introducing me to display: inline-block; -- I feel embarrassed for not knowing about it or having forgotten about it. I read your post here and using this instantly solved a problem I had resigned myself to avoiding instead of solving.

The production of the buttons is excellent. My only &#039;wobble&#039; is that I think some of the links that preceded them had some colour cues that I found myself using over the text. Now I need to read and it feels _slightly_ &#039;lumpy&#039;. But, as a trade off, probably much better now (buttons) than then (links/smaller click area etc). I would be intrigued to know if colour text on certain buttons was tested and rejected (some I _always_ use, other less so, guessing colour cues might even further improve this excellent and improving UI). Cheers!</description>
		<content:encoded><![CDATA[<p>THANK you for introducing me to display: inline-block; &#8212; I feel embarrassed for not knowing about it or having forgotten about it. I read your post here and using this instantly solved a problem I had resigned myself to avoiding instead of solving.</p>
<p>The production of the buttons is excellent. My only &#8216;wobble&#8217; is that I think some of the links that preceded them had some colour cues that I found myself using over the text. Now I need to read and it feels _slightly_ &#8216;lumpy&#8217;. But, as a trade off, probably much better now (buttons) than then (links/smaller click area etc). I would be intrigued to know if colour text on certain buttons was tested and rejected (some I _always_ use, other less so, guessing colour cues might even further improve this excellent and improving UI). Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lindsey</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4393</link>
		<dc:creator>Lindsey</dc:creator>
		<pubDate>Fri, 06 Feb 2009 12:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4393</guid>
		<description>Hi, First thing I noticed when I signed in to Gmail a few days ago was that they&#039;d messed up the buttons.

I found it considerably annoying that they removed the previous &#039;color coding&#039; that helped navigate the inbox bar. I also puzzled as to why they decided to make the buttons two tone, as it made it much harder to read. Maybe the &quot;faked gradient&quot; should be reworked, lightened, or skipped.</description>
		<content:encoded><![CDATA[<p>Hi, First thing I noticed when I signed in to Gmail a few days ago was that they&#8217;d messed up the buttons.</p>
<p>I found it considerably annoying that they removed the previous &#8216;color coding&#8217; that helped navigate the inbox bar. I also puzzled as to why they decided to make the buttons two tone, as it made it much harder to read. Maybe the &#8220;faked gradient&#8221; should be reworked, lightened, or skipped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ryan</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4392</link>
		<dc:creator>ryan</dc:creator>
		<pubDate>Fri, 06 Feb 2009 10:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4392</guid>
		<description>so i guess thats gonna land in gwt sometime?</description>
		<content:encoded><![CDATA[<p>so i guess thats gonna land in gwt sometime?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: greg elliott</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4391</link>
		<dc:creator>greg elliott</dc:creator>
		<pubDate>Fri, 06 Feb 2009 09:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4391</guid>
		<description>awesome write-up. thank you so much for sharing with us the process and motivation behind your (and google&#039;s) designs. i find this information extremely valuable in that it exposes the thoughts and considerations taken by exceptionally intelligent people, allowing us as readers to improve our own creative processes.

while it&#039;s definitely a chore to write up this kind of retrospective (as is documenting any work), i&#039;d love to see more articles like this from every discipline.

great work! =)</description>
		<content:encoded><![CDATA[<p>awesome write-up. thank you so much for sharing with us the process and motivation behind your (and google&#8217;s) designs. i find this information extremely valuable in that it exposes the thoughts and considerations taken by exceptionally intelligent people, allowing us as readers to improve our own creative processes.</p>
<p>while it&#8217;s definitely a chore to write up this kind of retrospective (as is documenting any work), i&#8217;d love to see more articles like this from every discipline.</p>
<p>great work! =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Jeffries</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4390</link>
		<dc:creator>Andy Jeffries</dc:creator>
		<pubDate>Fri, 06 Feb 2009 09:10:40 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4390</guid>
		<description>Great work on the buttons.  I have a strange request, is there any chance of getting a higher resolution copy of the visual spec image you&#039;ve put in the blog post.  I&#039;m new to speccing UI elements and leading a team of UI and backend developers here.</description>
		<content:encoded><![CDATA[<p>Great work on the buttons.  I have a strange request, is there any chance of getting a higher resolution copy of the visual spec image you&#8217;ve put in the blog post.  I&#8217;m new to speccing UI elements and leading a team of UI and backend developers here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4389</link>
		<dc:creator>Amy</dc:creator>
		<pubDate>Fri, 06 Feb 2009 08:04:14 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4389</guid>
		<description>Interesting write up!  I love the cleanliness of any implementation of using CSS instead of images.  One question though - why no rollovers on the &quot;more actions&quot; drop down?</description>
		<content:encoded><![CDATA[<p>Interesting write up!  I love the cleanliness of any implementation of using CSS instead of images.  One question though &#8211; why no rollovers on the &#8220;more actions&#8221; drop down?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Logan</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4388</link>
		<dc:creator>Thomas Logan</dc:creator>
		<pubDate>Fri, 06 Feb 2009 06:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4388</guid>
		<description>I second what Aaron said about adding ARIA (accessibility) support to the buttons so that they behave more like their desktop counterparts.  Check out http://codetalks.org to learn more.</description>
		<content:encoded><![CDATA[<p>I second what Aaron said about adding ARIA (accessibility) support to the buttons so that they behave more like their desktop counterparts.  Check out <a href="http://codetalks.org" rel="nofollow">http://codetalks.org</a> to learn more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Carver</title>
		<link>http://stopdesign.com/archive/2009/02/04/recreating-the-button.html#comment-4387</link>
		<dc:creator>Ryan Carver</dc:creator>
		<pubDate>Fri, 06 Feb 2009 04:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://stopdesign.com/?p=1827#comment-4387</guid>
		<description>Congrats, it&#039;s great to see this stuff go live. Thanks for the mention and best of luck on your continuing efforts to unify and improve the experience across products!</description>
		<content:encoded><![CDATA[<p>Congrats, it&#8217;s great to see this stuff go live. Thanks for the mention and best of luck on your continuing efforts to unify and improve the experience across products!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
