<?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: There is no solution for the Q element</title>
	<atom:link href="http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/</link>
	<description>Updates on the march of progress. A weblog about web design, standards, web browsers, and the overall health of the Web.</description>
	<lastBuildDate>Wed, 14 Dec 2011 14:45:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul</title>
		<link>http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/comment-page-1/#comment-3886</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 08 Feb 2007 02:34:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-3886</guid>
		<description>One way to deal with the lack of supprt for the Q tag is with the IE extension mechanism called behaviors.
I&#039;ve create a page with a behavior for this specific problem. I added the source and an explanation of it.
http://willcode4beer.com/tips.jsp?set=fixIEQuotes

For all of its problems, at least IE does give us the ability to fill the gaps. Of course, basic HTML support in a web browser would be nice too. ;-)</description>
		<content:encoded><![CDATA[<p>One way to deal with the lack of supprt for the Q tag is with the <abbr title="Internet Explorer">IE</abbr> extension mechanism called behaviors.<br />
I&#8217;ve create a page with a behavior for this specific problem. I added the source and an explanation of it.<br />
<a href="http://willcode4beer.com/tips.jsp?set=fixIEQuotes" rel="nofollow"><abbr title="HyperText Transfer Protocol">http</abbr>://willcode4beer.com/tips.<abbr title="Java Server Pages">jsp</abbr>?set=fixIEQuotes</a></p>
<p>For all of its problems, at least IE does give us the ability to fill the gaps. Of course, basic <abbr title="HyperText Markup Language">HTML</abbr> support in a web browser would be nice too. ;-)</p>
<p class="postdetails"><em>Posted using Mozilla Firefox 2.0.0.1 on Windows.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: someone</title>
		<link>http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/comment-page-1/#comment-1914</link>
		<dc:creator>someone</dc:creator>
		<pubDate>Tue, 31 Oct 2006 03:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1914</guid>
		<description>I don&#039;t think it matters. The standard clearly says what&#039;s supposed to happen, and anyone who uses a browser that doesn&#039;t support such an absurdly simple element should expect a suboptimal browsing experience.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it matters. The standard clearly says what&#8217;s supposed to happen, and anyone who uses a browser that doesn&#8217;t support such an absurdly simple element should expect a suboptimal browsing experience.</p>
<p class="postdetails"><em>Posted using Mozilla Firefox 3.0a on FreeBSD.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hammond</title>
		<link>http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/comment-page-1/#comment-1747</link>
		<dc:creator>David Hammond</dc:creator>
		<pubDate>Tue, 24 Oct 2006 19:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1747</guid>
		<description>That would more or less fix the issue for IE (with a ton of extra markup required), but as I said, IE isn&#039;t the only user agent that fails to support the &lt;code&gt;q&lt;/code&gt; element correctly. lynx will still show the page without quotes, as will a number of other user agents.</description>
		<content:encoded><![CDATA[<p>That would more or less fix the issue for <abbr title="Internet Explorer">IE</abbr> (with a ton of extra markup required), but as I said, IE isn&#8217;t the only user agent that fails to support the <code>q</code> element correctly. lynx will still show the page without quotes, as will a number of other user agents.</p>
<p class="postdetails"><em>Posted using Mozilla Firefox 1.5.0.7 on Windows.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roman</title>
		<link>http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/comment-page-1/#comment-1744</link>
		<dc:creator>Roman</dc:creator>
		<pubDate>Tue, 24 Oct 2006 18:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1744</guid>
		<description>The comment form decided to remove markup, so I would just describe it textually once again - a normal  element surrounded by two extra quotes. Each quote is hidden in IE conditional comment. The string inside comment should be similar to &quot;if lt IE N&quot;, where N = last version of IE without proper q support + 1. N should be incremented (by server-side magick) as more defective IE versions are released, and frozed if the issue is finally fixed by MS.</description>
		<content:encoded><![CDATA[<p>The comment form decided to remove markup, so I would just describe it textually once again &#8211; a normal  element surrounded by two extra quotes. Each quote is hidden in <abbr title="Internet Explorer">IE</abbr> conditional comment. The string inside comment should be similar to &#8220;if lt IE N&#8221;, where N = last version of IE without proper q support + 1. N should be incremented (by server-side magick) as more defective IE versions are released, and frozed if the issue is finally fixed by <abbr title="Microsoft">MS</abbr>.</p>
<p class="postdetails"><em>Posted using Opera 9.02 on Windows.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roman</title>
		<link>http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/comment-page-1/#comment-1743</link>
		<dc:creator>Roman</dc:creator>
		<pubDate>Tue, 24 Oct 2006 18:16:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdevout.net/tidings/2006/09/26/there-is-no-solution-for-the-q-element/#comment-1743</guid>
		<description>Wouldn&#039;t this work (I just enclosed extra quotes inside IE conditional comments)?
&lt;!--[if lt IE 8]&gt;&quot;--&gt;Text&lt;!--[if lt IE 8]&gt;&quot;--&gt;

All reasonable browsers will never see the extra quotes, while IE will always see the extra quotes - even if CSS did not load or was disabled.</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t this work (I just enclosed extra quotes inside <abbr title="Internet Explorer">IE</abbr> conditional comments)?<br />
<!--[if lt IE 8]&gt;"-->Text<!--[if lt IE 8]&gt;"--></p>
<p>All reasonable browsers will never see the extra quotes, while IE will always see the extra quotes &#8211; even if CSS did not load or was disabled.</p>
<p class="postdetails"><em>Posted using Opera 9.02 on Windows.</em></p>
]]></content:encoded>
	</item>
</channel>
</rss>
