<?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: Apple&#8217;s Pretty Search Bar</title>
	<atom:link href="http://www.gracepointafterfive.com/apple-search-bar/feed" rel="self" type="application/rss+xml" />
	<link>http://www.gracepointafterfive.com/apple-search-bar</link>
	<description>A design blog by those of us with day jobs</description>
	<lastBuildDate>Sun, 11 Jul 2010 08:27:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: abeyang</title>
		<link>http://www.gracepointafterfive.com/apple-search-bar/comment-page-1#comment-35</link>
		<dc:creator>abeyang</dc:creator>
		<pubDate>Tue, 04 Aug 2009 23:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.gracepointafterfive.com/?p=97#comment-35</guid>
		<description>@a: You&#039;re absolutely right. However, Pretty Search was developed for my company a few years ago, thus we had to comply with W3C&#039;s standards back then.

@Robert: Agreed. Even though it was designed specifically for my company, I made it abstract enough to be used anywhere. Unfortunately, I never got around to using it since then.

@David: That should work, too. Again, we were trying to abide by W3C&#039;s &quot;rules&quot; back then, which didn&#039;t allow for input=&quot;search&quot;. Rather than dealing with browsers separately, we went for a catch-all, cross-browser solution. With that said, I&#039;m very interested to see how you implemented your own Pretty Search in IE and Firefox!</description>
		<content:encoded><![CDATA[<p>@a: You&#8217;re absolutely right. However, Pretty Search was developed for my company a few years ago, thus we had to comply with W3C&#8217;s standards back then.</p>
<p>@Robert: Agreed. Even though it was designed specifically for my company, I made it abstract enough to be used anywhere. Unfortunately, I never got around to using it since then.</p>
<p>@David: That should work, too. Again, we were trying to abide by W3C&#8217;s &#8220;rules&#8221; back then, which didn&#8217;t allow for input=&#8221;search&#8221;. Rather than dealing with browsers separately, we went for a catch-all, cross-browser solution. With that said, I&#8217;m very interested to see how you implemented your own Pretty Search in IE and Firefox!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: a</title>
		<link>http://www.gracepointafterfive.com/apple-search-bar/comment-page-1#comment-34</link>
		<dc:creator>a</dc:creator>
		<pubDate>Tue, 04 Aug 2009 22:23:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.gracepointafterfive.com/?p=97#comment-34</guid>
		<description>Input type=search is allowed in W3C&#039;s HTML 5.</description>
		<content:encoded><![CDATA[<p>Input type=search is allowed in W3C&#8217;s HTML 5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Schultz</title>
		<link>http://www.gracepointafterfive.com/apple-search-bar/comment-page-1#comment-24</link>
		<dc:creator>Robert Schultz</dc:creator>
		<pubDate>Mon, 27 Jul 2009 16:10:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.gracepointafterfive.com/?p=97#comment-24</guid>
		<description>I subscribe to your blog and enjoy reading your posts :)

It would be great if you could post an &#039;example&#039; page, to show off your cool new search bar :)</description>
		<content:encoded><![CDATA[<p>I subscribe to your blog and enjoy reading your posts :)</p>
<p>It would be great if you could post an &#8216;example&#8217; page, to show off your cool new search bar :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Murdoch</title>
		<link>http://www.gracepointafterfive.com/apple-search-bar/comment-page-1#comment-23</link>
		<dc:creator>David Murdoch</dc:creator>
		<pubDate>Fri, 24 Jul 2009 13:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.gracepointafterfive.com/?p=97#comment-23</guid>
		<description>I&#039;m using the apple &quot;search&quot; input style on one of the websites I just completed.

Instead of browser sniffing you may be able to use a sort of feature detection:

        // try{} it to filter out IE (IE can&#039;t change the type of an input element without an error)...
        try {
            var searchHeight = searchInput.offsetHeight;
            searchInput.type = &quot;search&quot;;
            // if the input type did change to &quot;search&quot; and the offsetHeight stayed the same
            // we can use Safari &quot;search&quot; fields...
            if ( searchInput.type === &quot;search&quot; &amp;&amp; searchInput.offsetHeight === searchHeight ) {
                   document.getElementById(&quot;globalsearch&quot;).className += &quot; safari&quot;;
            }
            else {
                   searchInput.type=&quot;text&quot;;
                   throw &quot;exception&quot;&#039;;
            }
        }
        catch(e) {
               setUpSearchInputForOtherBrowsers();
        }


Also, &quot;a, input, textarea, select {outline:0}&quot; css rule should disable Safari&#039;s and Chrome&#039;s &quot;glow.&quot;</description>
		<content:encoded><![CDATA[<p>I&#8217;m using the apple &#8220;search&#8221; input style on one of the websites I just completed.</p>
<p>Instead of browser sniffing you may be able to use a sort of feature detection:</p>
<p>        // try{} it to filter out IE (IE can&#8217;t change the type of an input element without an error)&#8230;<br />
        try {<br />
            var searchHeight = searchInput.offsetHeight;<br />
            searchInput.type = &#8220;search&#8221;;<br />
            // if the input type did change to &#8220;search&#8221; and the offsetHeight stayed the same<br />
            // we can use Safari &#8220;search&#8221; fields&#8230;<br />
            if ( searchInput.type === &#8220;search&#8221; &amp;&amp; searchInput.offsetHeight === searchHeight ) {<br />
                   document.getElementById(&#8220;globalsearch&#8221;).className += &#8221; safari&#8221;;<br />
            }<br />
            else {<br />
                   searchInput.type=&#8221;text&#8221;;<br />
                   throw &#8220;exception&#8221;&#8216;;<br />
            }<br />
        }<br />
        catch(e) {<br />
               setUpSearchInputForOtherBrowsers();<br />
        }</p>
<p>Also, &#8220;a, input, textarea, select {outline:0}&#8221; css rule should disable Safari&#8217;s and Chrome&#8217;s &#8220;glow.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
