<?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: I&#8217;m a Recovering Browser Elitist</title>
	<atom:link href="http://geek.focalcurve.com/archive/2005/04/recovering-browser-elitist/feed/" rel="self" type="application/rss+xml" />
	<link>http://geek.focalcurve.com/archive/2005/04/recovering-browser-elitist/</link>
	<description>Pyrotechnics erupt in the distance. Guitar solo.</description>
	<lastBuildDate>Thu, 22 Jan 2009 02:20:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Joël kuiper</title>
		<link>http://geek.focalcurve.com/archive/2005/04/recovering-browser-elitist/comment-page-1/#comment-787</link>
		<dc:creator>Joël kuiper</dc:creator>
		<pubDate>Sat, 30 Apr 2005 11:15:25 +0000</pubDate>
		<guid isPermaLink="false">http://geek.focalcurve.com/archive/2005/04/help-me-overcome-browser-elitist/#comment-787</guid>
		<description>ignore that please...it will remove combined classes...
</description>
		<content:encoded><![CDATA[<p>ignore that please&#8230;it will remove combined classes&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joël kuiper</title>
		<link>http://geek.focalcurve.com/archive/2005/04/recovering-browser-elitist/comment-page-1/#comment-786</link>
		<dc:creator>Joël kuiper</dc:creator>
		<pubDate>Sat, 30 Apr 2005 11:13:43 +0000</pubDate>
		<guid isPermaLink="false">http://geek.focalcurve.com/archive/2005/04/help-me-overcome-browser-elitist/#comment-786</guid>
		<description>I actually think that replacing
&lt;code&gt;this.className = this.className.replace(/\b focus\b/, &quot;&quot;);&lt;/code&gt;
with
&lt;code&gt;this.className = this.setAttribute(&quot;class&quot;,&quot;&quot;);&lt;/code&gt;
is a better idea</description>
		<content:encoded><![CDATA[<p>I actually think that replacing<br />
<code>this.className = this.className.replace(/\b focus\b/, "");</code><br />
with<br />
<code>this.className = this.setAttribute("class","");</code><br />
is a better idea</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tino Zijdel</title>
		<link>http://geek.focalcurve.com/archive/2005/04/recovering-browser-elitist/comment-page-1/#comment-785</link>
		<dc:creator>Tino Zijdel</dc:creator>
		<pubDate>Sat, 30 Apr 2005 00:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://geek.focalcurve.com/archive/2005/04/help-me-overcome-browser-elitist/#comment-785</guid>
		<description>There should actually be something like an &#039;onrenderend&#039; event. The only other suitable option to append behavior to elements without the delay waiting for onload to occur is to polute your markup with inline scripts or use htc&#039;s (which in this case wouldn&#039;t be all that bad since it is for IE only).

Still I strongly advice against the sort of browser sniffing displayed here. Even Opera has the &#039;MSIE&#039; bit by default in it&#039;s useragent string nowadays to spoof browserdetections. UA-strings cannot be trusted. I also know of some 3rd party software that actually sents an empty or bogus string, even when using IE (I believe it&#039;s Norton Firewall - not very uncommon)...</description>
		<content:encoded><![CDATA[<p>There should actually be something like an &#8216;onrenderend&#8217; event. The only other suitable option to append behavior to elements without the delay waiting for onload to occur is to polute your markup with inline scripts or use htc&#8217;s (which in this case wouldn&#8217;t be all that bad since it is for IE only).</p>
<p>Still I strongly advice against the sort of browser sniffing displayed here. Even Opera has the &#8216;MSIE&#8217; bit by default in it&#8217;s useragent string nowadays to spoof browserdetections. UA-strings cannot be trusted. I also know of some 3rd party software that actually sents an empty or bogus string, even when using IE (I believe it&#8217;s Norton Firewall &#8211; not very uncommon)&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://geek.focalcurve.com/archive/2005/04/recovering-browser-elitist/comment-page-1/#comment-782</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Fri, 29 Apr 2005 20:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://geek.focalcurve.com/archive/2005/04/help-me-overcome-browser-elitist/#comment-782</guid>
		<description>Semantically, I&#039;m totally on the boat. I probably wouldn&#039;t use :hover or :focus to display a drop-down, for example. Events affecting the structure of a page should be handled by script, not CSS. The focused field gimmick seems presentational enough that I still believe :focus is kosher.</description>
		<content:encoded><![CDATA[<p>Semantically, I&#8217;m totally on the boat. I probably wouldn&#8217;t use :hover or :focus to display a drop-down, for example. Events affecting the structure of a page should be handled by script, not CSS. The focused field gimmick seems presentational enough that I still believe :focus is kosher.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Snook</title>
		<link>http://geek.focalcurve.com/archive/2005/04/recovering-browser-elitist/comment-page-1/#comment-781</link>
		<dc:creator>Jonathan Snook</dc:creator>
		<pubDate>Fri, 29 Apr 2005 17:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://geek.focalcurve.com/archive/2005/04/help-me-overcome-browser-elitist/#comment-781</guid>
		<description>I suspect the number of people who have javascript turned off is a small minority. 

In any case, I&#039;m just arguing the semantics of the issue. I&#039;d have done the same as you. In fact, the input&#039;s on my page use :focus and I didn&#039;t even include an IE fallback. :)</description>
		<content:encoded><![CDATA[<p>I suspect the number of people who have javascript turned off is a small minority. </p>
<p>In any case, I&#8217;m just arguing the semantics of the issue. I&#8217;d have done the same as you. In fact, the input&#8217;s on my page use :focus and I didn&#8217;t even include an IE fallback. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
