<?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 Working Group latest resolutions</title>
	<atom:link href="http://www.css3.info/css-working-group-latest-resolutions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.css3.info/css-working-group-latest-resolutions/</link>
	<description>All you ever needed to know about CSS3</description>
	<lastBuildDate>Tue, 07 Feb 2012 18:52:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Brendan Falkowski</title>
		<link>http://www.css3.info/css-working-group-latest-resolutions/comment-page-1/#comment-140386</link>
		<dc:creator>Brendan Falkowski</dc:creator>
		<pubDate>Mon, 14 Apr 2008 16:31:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/?p=276#comment-140386</guid>
		<description>Tree-line lists would be nice, but aren&#039;t semantically obvious. Defining a list as a tree doesn&#039;t offer any benefit in terms of organization, it&#039;s purely decorative. Still would be nice.</description>
		<content:encoded><![CDATA[<p>Tree-line lists would be nice, but aren&#8217;t semantically obvious. Defining a list as a tree doesn&#8217;t offer any benefit in terms of organization, it&#8217;s purely decorative. Still would be nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fatih Hayrioğlu&#8217;nun not defteri &#187; 08 Nisan 2008 web&#8217;den seçme haberler</title>
		<link>http://www.css3.info/css-working-group-latest-resolutions/comment-page-1/#comment-136831</link>
		<dc:creator>Fatih Hayrioğlu&#8217;nun not defteri &#187; 08 Nisan 2008 web&#8217;den seçme haberler</dc:creator>
		<pubDate>Wed, 09 Apr 2008 18:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/?p=276#comment-136831</guid>
		<description>[...] CSS çalışma grubunun son toplantısından sonra alınan sonuçlar ve özet. Bağlantı [...]</description>
		<content:encoded><![CDATA[<p>[...] CSS çalışma grubunun son toplantısından sonra alınan sonuçlar ve özet. Bağlantı [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Dabell</title>
		<link>http://www.css3.info/css-working-group-latest-resolutions/comment-page-1/#comment-133741</link>
		<dc:creator>Jim Dabell</dc:creator>
		<pubDate>Mon, 07 Apr 2008 10:39:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/?p=276#comment-133741</guid>
		<description>One thing that stuck out like a sore thumb:

&gt; Scriptable Selectors

&gt; Idea was that a selector accepts a JavaScript function that returns true or false, determining whether the selector matches or not. VERY strong reservations about this from implementors: executing functions during selector matching is scary, particularly if those functions are allowed to modify the elements during matching!

&gt; Alternate idea is to define a set of tokens on the element node, allow scripts to add and remove tokens, and match against that set.. thereby avoiding the execution of any functions during style matching.

Don&#039;t we already have that alternate idea?  We call those tokens &quot;classes&quot;.</description>
		<content:encoded><![CDATA[<p>One thing that stuck out like a sore thumb:</p>
<p>&gt; Scriptable Selectors</p>
<p>&gt; Idea was that a selector accepts a JavaScript function that returns true or false, determining whether the selector matches or not. VERY strong reservations about this from implementors: executing functions during selector matching is scary, particularly if those functions are allowed to modify the elements during matching!</p>
<p>&gt; Alternate idea is to define a set of tokens on the element node, allow scripts to add and remove tokens, and match against that set.. thereby avoiding the execution of any functions during style matching.</p>
<p>Don&#8217;t we already have that alternate idea?  We call those tokens &#8220;classes&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CSS WG F2F in San Diego - feature resolutions besides&#8230; :: Coding and Dreaming</title>
		<link>http://www.css3.info/css-working-group-latest-resolutions/comment-page-1/#comment-133478</link>
		<dc:creator>CSS WG F2F in San Diego - feature resolutions besides&#8230; :: Coding and Dreaming</dc:creator>
		<pubDate>Sun, 06 Apr 2008 22:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/?p=276#comment-133478</guid>
		<description>[...] A recent post on CSS3.Info regarding the CSS WG F2F in San Diego nicely sums up resolutions relating to possible up-coming CSS features. [...]</description>
		<content:encoded><![CDATA[<p>[...] A recent post on CSS3.Info regarding the CSS WG F2F in San Diego nicely sums up resolutions relating to possible up-coming CSS features. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Thomassen</title>
		<link>http://www.css3.info/css-working-group-latest-resolutions/comment-page-1/#comment-133275</link>
		<dc:creator>Thomas Thomassen</dc:creator>
		<pubDate>Sun, 06 Apr 2008 14:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/?p=276#comment-133275</guid>
		<description>I like the idea of constants. Very often I wished that I could define a set of colour constants and refer to them so I won&#039;t have to search and replace every occurrence when I modify the colour scheme.</description>
		<content:encoded><![CDATA[<p>I like the idea of constants. Very often I wished that I could define a set of colour constants and refer to them so I won&#8217;t have to search and replace every occurrence when I modify the colour scheme.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.css3.info/css-working-group-latest-resolutions/comment-page-1/#comment-131938</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Fri, 04 Apr 2008 17:28:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/?p=276#comment-131938</guid>
		<description>In part IV, the centering stuff was quite interesting.

I agree, that if I want to apply a &quot;centering&quot; it is only to a specified container... I do not want any children to inherit this centering.

Good progress!</description>
		<content:encoded><![CDATA[<p>In part IV, the centering stuff was quite interesting.</p>
<p>I agree, that if I want to apply a &#8220;centering&#8221; it is only to a specified container&#8230; I do not want any children to inherit this centering.</p>
<p>Good progress!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jive</title>
		<link>http://www.css3.info/css-working-group-latest-resolutions/comment-page-1/#comment-131786</link>
		<dc:creator>jive</dc:creator>
		<pubDate>Fri, 04 Apr 2008 13:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/?p=276#comment-131786</guid>
		<description>Looks like they are talking about doing &quot;text-orientation&quot; so you can do vertical text. Hopefully that will make it.</description>
		<content:encoded><![CDATA[<p>Looks like they are talking about doing &#8220;text-orientation&#8221; so you can do vertical text. Hopefully that will make it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neal G</title>
		<link>http://www.css3.info/css-working-group-latest-resolutions/comment-page-1/#comment-131779</link>
		<dc:creator>Neal G</dc:creator>
		<pubDate>Fri, 04 Apr 2008 13:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.css3.info/?p=276#comment-131779</guid>
		<description>Wow, looks like the group has been very busy. I dig the constants and tree-lines proposals.</description>
		<content:encoded><![CDATA[<p>Wow, looks like the group has been very busy. I dig the constants and tree-lines proposals.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!--
This site's performance optimized by W3 Total Cache:

W3 Total Cache improves the user experience of your blog by caching
frequent operations, reducing the weight of various files and providing
transparent content delivery network integration.

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/


Served from: css3.info @ 2012-02-08 10:05:05 -->
