<?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: The Q tag, cross browser compatibility and the Content property</title>
	<atom:link href="http://jhop.me/browsers/the-q-element-cross-browser-compatibility-and-the-content-property/feed" rel="self" type="application/rss+xml" />
	<link>http://jhop.me/browsers/the-q-element-cross-browser-compatibility-and-the-content-property</link>
	<description></description>
	<lastBuildDate>Tue, 11 May 2010 20:47:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James Hopkins</title>
		<link>http://jhop.me/browsers/the-q-element-cross-browser-compatibility-and-the-content-property/comment-page-1#comment-11</link>
		<dc:creator>James Hopkins</dc:creator>
		<pubDate>Sun, 16 Mar 2008 13:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://idreamincode.co.uk/browsers/the-q-element-cross-browser-compatibility-and-the-content-property#comment-11</guid>
		<description>Brett, good point you raise, and thanks for the comments. I totally agree with what you say with regards to web standards and achieving a usable end product, and there&#039;s a thin line between coding purity and cross-browser compliancy. However I personally think that in the context of my example, there&#039;s some room to manoeuvre.

The main point of my article was to make readers aware more than anything, that the technique described by Eric, a) goes against the W3C guidlines, and b) plays around with the correct, default behaviour of standards compliant browsers- certainly &lt;strong&gt;not&lt;/strong&gt; best practice. At the end of the day it&#039;s down to the individual developer as to what he/she deems to be an acceptable balance between coding purity and cross browser compliancy</description>
		<content:encoded><![CDATA[<p>Brett, good point you raise, and thanks for the comments. I totally agree with what you say with regards to web standards and achieving a usable end product, and there&#8217;s a thin line between coding purity and cross-browser compliancy. However I personally think that in the context of my example, there&#8217;s some room to manoeuvre.</p>
<p>The main point of my article was to make readers aware more than anything, that the technique described by Eric, a) goes against the W3C guidlines, and b) plays around with the correct, default behaviour of standards compliant browsers- certainly <strong>not</strong> best practice. At the end of the day it&#8217;s down to the individual developer as to what he/she deems to be an acceptable balance between coding purity and cross browser compliancy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Clements</title>
		<link>http://jhop.me/browsers/the-q-element-cross-browser-compatibility-and-the-content-property/comment-page-1#comment-10</link>
		<dc:creator>Brett Clements</dc:creator>
		<pubDate>Fri, 14 Mar 2008 18:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://idreamincode.co.uk/browsers/the-q-element-cross-browser-compatibility-and-the-content-property#comment-10</guid>
		<description>Thanks for your article - it was interesting to read.

From a purist&#039;s coding point of view I totally agree with what you&#039;re saying, however you know as well as I do that the vast majority of users still use IE, (roughly 75%  - depending on who&#039;s providing the stats), and I doubt that will change anytime in the near future. We can still dream though :)

As much as I applaud your stance on web standards I think you need to remember that coding with web standards is not an end in itself but rather a means to an end and that end is to create the best web user experience possible for everyone who chooses to view our websites no matter what browser they choose to use. Most web users don&#039;t really care what coding techniques we developers use but rather whether they can use a particular website or not.
As much as developers like you and I need to strive to produce near &#039;perfect&#039; code, we need to keep the end user in mind and be careful not to alienate the very people the end result was intended for.

Keep up the good work and enthusiasm  -  you never know.....one day all browsers may see the &#039;light&#039; but until then lets not forget why we do what we do  :)</description>
		<content:encoded><![CDATA[<p>Thanks for your article &#8211; it was interesting to read.</p>
<p>From a purist&#8217;s coding point of view I totally agree with what you&#8217;re saying, however you know as well as I do that the vast majority of users still use IE, (roughly 75%  &#8211; depending on who&#8217;s providing the stats), and I doubt that will change anytime in the near future. We can still dream though <img src='http://jhop.me/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>As much as I applaud your stance on web standards I think you need to remember that coding with web standards is not an end in itself but rather a means to an end and that end is to create the best web user experience possible for everyone who chooses to view our websites no matter what browser they choose to use. Most web users don&#8217;t really care what coding techniques we developers use but rather whether they can use a particular website or not.<br />
As much as developers like you and I need to strive to produce near &#8216;perfect&#8217; code, we need to keep the end user in mind and be careful not to alienate the very people the end result was intended for.</p>
<p>Keep up the good work and enthusiasm  &#8211;  you never know&#8230;..one day all browsers may see the &#8216;light&#8217; but until then lets not forget why we do what we do  <img src='http://jhop.me/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
