<?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: CSS 3: A Giant Serving Of FAIL</title>
	<atom:link href="http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/feed/" rel="self" type="application/rss+xml" />
	<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 21:30:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Continuing Intermittent Incoherency &#187; CSS 3: Progress!</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-236307</link>
		<dc:creator>Continuing Intermittent Incoherency &#187; CSS 3: Progress!</dc:creator>
		<pubDate>Fri, 21 Aug 2009 00:52:54 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-236307</guid>
		<description>[...] of days regarding how effective (or not) the CSS Working Group has been. I&#8217;ve been pretty brutal in my critique in the past (and much of it still stands), but there&#8217;s reason to [...]</description>
		<content:encoded><![CDATA[<p>[...] of days regarding how effective (or not) the CSS Working Group has been. I&#8217;ve been pretty brutal in my critique in the past (and much of it still stands), but there&#8217;s reason to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CSS Variables Are The Future &#124; Continuing Intermittent Incoherency</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-234933</link>
		<dc:creator>CSS Variables Are The Future &#124; Continuing Intermittent Incoherency</dc:creator>
		<pubDate>Mon, 11 Aug 2008 11:54:50 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-234933</guid>
		<description>[...] But where the spec is in-front of the important implementations&#8230;well, I&#8217;ve ranted before on the topic. CSS sucks, and the editor of the spec has now written at length of his intent to keep [...]</description>
		<content:encoded><![CDATA[<p>[...] But where the spec is in-front of the important implementations&#8230;well, I&#8217;ve ranted before on the topic. CSS sucks, and the editor of the spec has now written at length of his intent to keep [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oda kapisi</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-225192</link>
		<dc:creator>oda kapisi</dc:creator>
		<pubDate>Fri, 18 Jan 2008 13:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-225192</guid>
		<description>It would be great to be able to vote somewhere for W3C spec ideas &amp; recommendations.</description>
		<content:encoded><![CDATA[<p>It would be great to be able to vote somewhere for W3C spec ideas &amp; recommendations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oda kapisi</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-225189</link>
		<dc:creator>oda kapisi</dc:creator>
		<pubDate>Fri, 18 Jan 2008 13:08:46 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-225189</guid>
		<description>I guess this is why I’ve been generating my CSS files programmatically for some time!!...</description>
		<content:encoded><![CDATA[<p>I guess this is why I’ve been generating my CSS files programmatically for some time!!&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stubbornella &#187; Blog Archive &#187; CSS 3 and where we shouldn&#8217;t be</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-218501</link>
		<dc:creator>Stubbornella &#187; Blog Archive &#187; CSS 3 and where we shouldn&#8217;t be</dc:creator>
		<pubDate>Sun, 23 Dec 2007 11:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-218501</guid>
		<description>[...] It amuses me that someone who says,  CSS 3 is a joke. A sad, sick joke being perpetrated by people who clearly don’t build actual web apps. [...]</description>
		<content:encoded><![CDATA[<p>[...] It amuses me that someone who says,  CSS 3 is a joke. A sad, sick joke being perpetrated by people who clearly don’t build actual web apps. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Continuing Intermittent Incoherency &#187; The W3C Cannot Save Us</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-215621</link>
		<dc:creator>Continuing Intermittent Incoherency &#187; The W3C Cannot Save Us</dc:creator>
		<pubDate>Sun, 16 Dec 2007 23:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-215621</guid>
		<description>[...] But all is not well, nor has it been for a long, long time. No work on hbox or vbox or mixins/inheritance. There&#8217;s no indication that the WG has taken stabs exposing the expressive power that Microsoft did with their CSS expressions implementation. Ugg. [...]</description>
		<content:encoded><![CDATA[<p>[...] But all is not well, nor has it been for a long, long time. No work on hbox or vbox or mixins/inheritance. There&#8217;s no indication that the WG has taken stabs exposing the expressive power that Microsoft did with their CSS expressions implementation. Ugg. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CSS 3: A Giant Serving Of FAIL &#171; turnings</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-199419</link>
		<dc:creator>CSS 3: A Giant Serving Of FAIL &#171; turnings</dc:creator>
		<pubDate>Wed, 14 Nov 2007 14:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-199419</guid>
		<description>[...] CSS 3: A Giant Serving Of&#160;FAIL  14 11 2007    CSS 3: A Giant Serving Of FAIL: [...]</description>
		<content:encoded><![CDATA[<p>[...] CSS 3: A Giant Serving Of&nbsp;FAIL  14 11 2007    CSS 3: A Giant Serving Of FAIL: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The CSS3 Soapbox! &#187; Blog Archive &#187; &#187; Recent Perspectives on the CSS Working Group and CSS3</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-197274</link>
		<dc:creator>The CSS3 Soapbox! &#187; Blog Archive &#187; &#187; Recent Perspectives on the CSS Working Group and CSS3</dc:creator>
		<pubDate>Fri, 09 Nov 2007 15:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-197274</guid>
		<description>[...] Alex Russell starts a discussion of CSS3 as a failure. [...]</description>
		<content:encoded><![CDATA[<p>[...] Alex Russell starts a discussion of CSS3 as a failure. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Continuing Intermittent Incoherency &#187; The Strangely Charged ES4 &#8220;Debate&#8221;</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-194635</link>
		<dc:creator>Continuing Intermittent Incoherency &#187; The Strangely Charged ES4 &#8220;Debate&#8221;</dc:creator>
		<pubDate>Fri, 02 Nov 2007 08:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-194635</guid>
		<description>[...] We&#8217;ve seen both of these voices before, particularly in regards to W3C activities. Some of my previous comments on that topic made the debate louder without (I&#8217;m afraid) providing much perspective about how the community can effectively advocate for fixes. What&#8217;s good about the ES4 debate (in contrast w/ my CSS ramblings) is that they are scoped to particular implementers. Insofar as advocacy makes a difference, lobbying a working group which is moribund is nearly useless. They have authority but no power. Power in these situations always lies with implementers, aka browser vendors. The CSS discussions are weird and airy because there&#8217;s no real skin in the game. Swatting at the W3C is just so much shadow boxing. Asking browser vendors to take risks, to show some good old-fashioned technical leadership and put some of their theories about how to evolve into their competing implementations&#8230;.now that&#8217;s got legs. [...]</description>
		<content:encoded><![CDATA[<p>[...] We&#8217;ve seen both of these voices before, particularly in regards to W3C activities. Some of my previous comments on that topic made the debate louder without (I&#8217;m afraid) providing much perspective about how the community can effectively advocate for fixes. What&#8217;s good about the ES4 debate (in contrast w/ my CSS ramblings) is that they are scoped to particular implementers. Insofar as advocacy makes a difference, lobbying a working group which is moribund is nearly useless. They have authority but no power. Power in these situations always lies with implementers, aka browser vendors. The CSS discussions are weird and airy because there&#8217;s no real skin in the game. Swatting at the W3C is just so much shadow boxing. Asking browser vendors to take risks, to show some good old-fashioned technical leadership and put some of their theories about how to evolve into their competing implementations&#8230;.now that&#8217;s got legs. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tercüme bürosu</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-193778</link>
		<dc:creator>Tercüme bürosu</dc:creator>
		<pubDate>Tue, 30 Oct 2007 15:39:39 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-193778</guid>
		<description>I guess this is why I’ve been generating my CSS files programmatically for some time!!</description>
		<content:encoded><![CDATA[<p>I guess this is why I’ve been generating my CSS files programmatically for some time!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Silvashy</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-189692</link>
		<dc:creator>Joseph Silvashy</dc:creator>
		<pubDate>Thu, 18 Oct 2007 21:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-189692</guid>
		<description>I would like to say that, at this point in time I am probably more comfortable with all the workarounds I use to achieve the effects that CSS3 claims to do &quot;so easily&quot; that I would rather stick to my workarounds entirely, other things are proving to be more useful than  our never coming CSS3 anyway, like DOM scripting in the general sense, even though CSS relies heavily on the DOM.</description>
		<content:encoded><![CDATA[<p>I would like to say that, at this point in time I am probably more comfortable with all the workarounds I use to achieve the effects that CSS3 claims to do &#8220;so easily&#8221; that I would rather stick to my workarounds entirely, other things are proving to be more useful than  our never coming CSS3 anyway, like DOM scripting in the general sense, even though CSS relies heavily on the DOM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: developercast.com &#187; CSS Positioning: Three Specs Better than One?</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-187600</link>
		<dc:creator>developercast.com &#187; CSS Positioning: Three Specs Better than One?</dc:creator>
		<pubDate>Fri, 12 Oct 2007 03:51:26 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-187600</guid>
		<description>[...] Introduced by the W3C as a working draft in December 2005, there&#8217;s no denying the CSS Advanced Layout module is way better than what we have now, but the apparent lack of interest from browser vendors in implementing this module suggests it might be on the wrong track. Following the release of the latest working draft in August, SitePen&#8217;s Alex Russell had some harsh criticism: [...]</description>
		<content:encoded><![CDATA[<p>[...] Introduced by the W3C as a working draft in December 2005, there&#8217;s no denying the CSS Advanced Layout module is way better than what we have now, but the apparent lack of interest from browser vendors in implementing this module suggests it might be on the wrong track. Following the release of the latest working draft in August, SitePen&#8217;s Alex Russell had some harsh criticism: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SitePoint Blogs &#187; CSS Positioning: Three Specs Better than One?</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-187594</link>
		<dc:creator>SitePoint Blogs &#187; CSS Positioning: Three Specs Better than One?</dc:creator>
		<pubDate>Fri, 12 Oct 2007 03:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-187594</guid>
		<description>[...] Introduced by the W3C as a working draft in December 2005, there&#8217;s no denying the CSS Advanced Layout module is way better than what we have now, but the apparent lack of interest from browser vendors in implementing this module suggests it might be on the wrong track. Following the release of the latest working draft in August, SitePen&#8217;s Alex Russell had some harsh criticism: [...]</description>
		<content:encoded><![CDATA[<p>[...] Introduced by the W3C as a working draft in December 2005, there&#8217;s no denying the CSS Advanced Layout module is way better than what we have now, but the apparent lack of interest from browser vendors in implementing this module suggests it might be on the wrong track. Following the release of the latest working draft in August, SitePen&#8217;s Alex Russell had some harsh criticism: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Standardy sieciowe - (x)HTML, CSS i nie tylko...</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-183055</link>
		<dc:creator>Standardy sieciowe - (x)HTML, CSS i nie tylko...</dc:creator>
		<pubDate>Sat, 29 Sep 2007 23:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-183055</guid>
		<description>[...] Chodzi mi o świetny artykuł Alexa Russella. Uważa on, iż tak istotne kwestie jak dziedziczenie zapisów i możliwość tworzenia własnych zmiennych powinny być już ujęte w CSS 2. Okazuje się, że w wersji roboczej CSS 3 również tych zagadnień nie znajdziemy - w zamian osoby pracujące nad rozwojem CSS skupiają się na mniej ambitnych celach. Faktem jest, że na chwilę obecną kwestia dziedziczenia jest mocno zaniedbana. Pozostajemy przy dziedziczeniu klas w kodzie HTML, ale co z samym CSS? Przecież często narzuca się, aby zaimportować do jakiejś klasy inną - wcześniej zdefiniowaną o uniwersalnym charakterze. Niestety takiego mieszania klas zrobić się nie da - pozostaje mozolne dopisanie wartości, co niewątpliwie wpływa na puchnięcie całego kodu. [...]</description>
		<content:encoded><![CDATA[<p>[...] Chodzi mi o świetny artykuł Alexa Russella. Uważa on, iż tak istotne kwestie jak dziedziczenie zapisów i możliwość tworzenia własnych zmiennych powinny być już ujęte w CSS 2. Okazuje się, że w wersji roboczej CSS 3 również tych zagadnień nie znajdziemy &#8211; w zamian osoby pracujące nad rozwojem CSS skupiają się na mniej ambitnych celach. Faktem jest, że na chwilę obecną kwestia dziedziczenia jest mocno zaniedbana. Pozostajemy przy dziedziczeniu klas w kodzie HTML, ale co z samym CSS? Przecież często narzuca się, aby zaimportować do jakiejś klasy inną &#8211; wcześniej zdefiniowaną o uniwersalnym charakterze. Niestety takiego mieszania klas zrobić się nie da &#8211; pozostaje mozolne dopisanie wartości, co niewątpliwie wpływa na puchnięcie całego kodu. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Missing Features &#187; Building a Better Standards Group</title>
		<link>http://infrequently.org/2007/09/css-3-a-giant-serving-of-fail/comment-page-2/#comment-182807</link>
		<dc:creator>Missing Features &#187; Building a Better Standards Group</dc:creator>
		<pubDate>Fri, 28 Sep 2007 13:49:47 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=625#comment-182807</guid>
		<description>[...] Alex Russell, lead architect of the insanely beautiful Dojo framework correctly points out in a recent post that the CSS3 spec is dead on arrival. Indeed, Alex aptly points out that the W3C has failed its mission wholesale of &#8220;Leading the web to it&#8217;s full potential&#8230;&#8221;. [...]</description>
		<content:encoded><![CDATA[<p>[...] Alex Russell, lead architect of the insanely beautiful Dojo framework correctly points out in a recent post that the CSS3 spec is dead on arrival. Indeed, Alex aptly points out that the W3C has failed its mission wholesale of &#8220;Leading the web to it&#8217;s full potential&#8230;&#8221;. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

