<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Proposal for a CSS ancestor grouping syntax</title>
	<link>http://www.feike.biz/weblog/2008/07/23/proposal-for-a-css-ancestor-grouping-syntax/</link>
	<description>Observing trends in computer technology and internet business</description>
	<pubDate>Fri, 21 Nov 2008 06:51:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: Paris Holley</title>
		<link>http://www.feike.biz/weblog/2008/07/23/proposal-for-a-css-ancestor-grouping-syntax/#comment-769</link>
		<author>Paris Holley</author>
		<pubDate>Wed, 23 Jul 2008 14:34:36 +0000</pubDate>
		<guid>http://www.feike.biz/weblog/2008/07/23/proposal-for-a-css-ancestor-grouping-syntax/#comment-769</guid>
					<description>That is an interesting concept and I am up for anything that would help consolidate CSS files. Only issue I can see coming up is if that change to syntax would cause CSS rendering to become slower due to the additional parsing of rules by the browser. As rarely as CSS files are accessed, I don't think that the CSS saved using that method would be beneficial to the user. There is also the issue with backwards compatibility, because this will surely not work on browsers that do not adapt this spec. Things to think about it...</description>
		<content:encoded><![CDATA[<p>That is an interesting concept and I am up for anything that would help consolidate CSS files. Only issue I can see coming up is if that change to syntax would cause CSS rendering to become slower due to the additional parsing of rules by the browser. As rarely as CSS files are accessed, I don&#8217;t think that the CSS saved using that method would be beneficial to the user. There is also the issue with backwards compatibility, because this will surely not work on browsers that do not adapt this spec. Things to think about it&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Greg</title>
		<link>http://www.feike.biz/weblog/2008/07/23/proposal-for-a-css-ancestor-grouping-syntax/#comment-771</link>
		<author>Greg</author>
		<pubDate>Wed, 23 Jul 2008 18:51:37 +0000</pubDate>
		<guid>http://www.feike.biz/weblog/2008/07/23/proposal-for-a-css-ancestor-grouping-syntax/#comment-771</guid>
					<description>What I'd really like to see is being able to modify an element's style if it contains another element, such as:

tr &#60; td &#60; input[type=checkbox][checked] {
background-color: grey;
}

The style would apply to the tr element that had a child td that had a child checkbox that was checked.  So you could highlight rows if a checkbox is checked in that row.  There would be other useful scenarios, but that's the most obvious.  It's annoying to have to use javascript to accomplish that.  Then again, it might be insanely difficult and/or processor-intensive to allow for that in browsers, I don't know.

(resubmitted because the server thought my markup was html and removed it)</description>
		<content:encoded><![CDATA[<p>What I&#8217;d really like to see is being able to modify an element&#8217;s style if it contains another element, such as:</p>
<p>tr &lt; td &lt; input[type=checkbox][checked] {<br />
background-color: grey;<br />
}</p>
<p>The style would apply to the tr element that had a child td that had a child checkbox that was checked.  So you could highlight rows if a checkbox is checked in that row.  There would be other useful scenarios, but that&#8217;s the most obvious.  It&#8217;s annoying to have to use javascript to accomplish that.  Then again, it might be insanely difficult and/or processor-intensive to allow for that in browsers, I don&#8217;t know.</p>
<p>(resubmitted because the server thought my markup was html and removed it)</p>
]]></content:encoded>
				</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 3.208 seconds -->
