<?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: In Defense of Vendor Prefixes</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/</link>
	<description>Things that Eric A. Meyer, CSS expert, writes about on his personal Web site; it&#039;s largely Web standards and Web technology, but also various bits of culture, politics, personal observations, and other miscellaneous stuff</description>
	<lastBuildDate>Fri, 10 May 2013 11:50:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Erik</title>
		<link>http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/#comment-509947</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Wed, 15 Sep 2010 15:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1360#comment-509947</guid>
		<description><![CDATA[Honestly you could probably say the most random craziest thing and people would agree with you. Because people trust you. You are are the best of the best. A lot of people don&#039;t think for themselves. You have a lot of influence on today&#039;s standards and practices and people know it. Some follow blindly.

But, you are trusted for a reason. You&#039;ve not yet lead us astray.]]></description>
		<content:encoded><![CDATA[<p>Honestly you could probably say the most random craziest thing and people would agree with you. Because people trust you. You are are the best of the best. A lot of people don&#8217;t think for themselves. You have a lot of influence on today&#8217;s standards and practices and people know it. Some follow blindly.</p>
<p>But, you are trusted for a reason. You&#8217;ve not yet lead us astray.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/#comment-506653</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 05 Aug 2010 16:02:19 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1360#comment-506653</guid>
		<description><![CDATA[To be honest, I sort of wish every property could have a vender specific prefix, not just the in progress ones.

Every now and then, for reasons you can&#039;t figure, you need to get Webkit to have a different line height than other browsers, or Firefox needs a different width, or IE needs a different margin and you just wish you could: 
p { line-height: 22px; -webkit-line-height: 24px; }]]></description>
		<content:encoded><![CDATA[<p>To be honest, I sort of wish every property could have a vender specific prefix, not just the in progress ones.</p>
<p>Every now and then, for reasons you can&#8217;t figure, you need to get Webkit to have a different line height than other browsers, or Firefox needs a different width, or IE needs a different margin and you just wish you could:<br />
p { line-height: 22px; -webkit-line-height: 24px; }</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/#comment-504869</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Sun, 18 Jul 2010 16:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1360#comment-504869</guid>
		<description><![CDATA[Any predictions for how browsers can prefix CSS3 features that aren&#039;t properties like -moz-border-radius? I&#039;ve seen on css3.info that Firefox 4 will bring -moz-calc() which is cool, but I wonder how one would prefix, say, the new &quot;rem&quot; unit (http://www.w3.org/TR/css3-values/#relative).]]></description>
		<content:encoded><![CDATA[<p>Any predictions for how browsers can prefix CSS3 features that aren&#8217;t properties like -moz-border-radius? I&#8217;ve seen on css3.info that Firefox 4 will bring -moz-calc() which is cool, but I wonder how one would prefix, say, the new &#8220;rem&#8221; unit (<a href="http://www.w3.org/TR/css3-values/#relative" rel="nofollow">http://www.w3.org/TR/css3-values/#relative</a>).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Fink</title>
		<link>http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/#comment-504322</link>
		<dc:creator>Richard Fink</dc:creator>
		<pubDate>Mon, 12 Jul 2010 00:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1360#comment-504322</guid>
		<description><![CDATA[&quot;it’s actually that I merely articulated what most people had already instinctively decided for themselves.&quot;

True for me. Glad someone with your standing brought it to the fore. I only hope implementors reach a consensus on best-practice for prefixes. Like any system, predictability and consistency are key.]]></description>
		<content:encoded><![CDATA[<p>&#8220;it’s actually that I merely articulated what most people had already instinctively decided for themselves.&#8221;</p>
<p>True for me. Glad someone with your standing brought it to the fore. I only hope implementors reach a consensus on best-practice for prefixes. Like any system, predictability and consistency are key.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miles</title>
		<link>http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/#comment-503874</link>
		<dc:creator>Miles</dc:creator>
		<pubDate>Wed, 07 Jul 2010 22:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1360#comment-503874</guid>
		<description><![CDATA[The prefixes are intentional, its as simple as that. Which means we can make them what we want them to be.

It becomes a win-win for authors that want a way to &quot;filter&quot; for different browsers and their capabilities, and its a way for vendors that want to test something and see what works and get feedback.]]></description>
		<content:encoded><![CDATA[<p>The prefixes are intentional, its as simple as that. Which means we can make them what we want them to be.</p>
<p>It becomes a win-win for authors that want a way to &#8220;filter&#8221; for different browsers and their capabilities, and its a way for vendors that want to test something and see what works and get feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael C.</title>
		<link>http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/#comment-503858</link>
		<dc:creator>Michael C.</dc:creator>
		<pubDate>Wed, 07 Jul 2010 20:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1360#comment-503858</guid>
		<description><![CDATA[Indeed, and I think that anyone &quot;advanced&quot; enough in CSS to be aware of vendor prefixes is most likely someone who also went through /* the pai\n of &quot;\&quot;}\&quot;&quot; various @hacks \*/.]]></description>
		<content:encoded><![CDATA[<p>Indeed, and I think that anyone &#8220;advanced&#8221; enough in CSS to be aware of vendor prefixes is most likely someone who also went through /* the pai\n of &#8220;\&#8221;}\&#8221;" various @hacks \*/.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephanie Hobson</title>
		<link>http://meyerweb.com/eric/thoughts/2010/07/07/in-defense-of-vendor-prefixes/#comment-503846</link>
		<dc:creator>Stephanie Hobson</dc:creator>
		<pubDate>Wed, 07 Jul 2010 18:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1360#comment-503846</guid>
		<description><![CDATA[The annoyance factor of prefixes is less than the annoyance factor of hacks ;)]]></description>
		<content:encoded><![CDATA[<p>The annoyance factor of prefixes is less than the annoyance factor of hacks ;)</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! -->