<?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: Identifying text-only nodes with CSS</title>
	<atom:link href="http://alastairc.ac/2006/10/text-nodes-and-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://alastairc.ac/2006/10/text-nodes-and-css/</link>
	<description>Kything web interactions</description>
	<lastBuildDate>Fri, 13 Apr 2012 05:33:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: AlastairC</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-59282</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Fri, 11 Jul 2008 07:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-59282</guid>
		<description>I&#039;d rather not open links in a new window (and definitely not without warning the user - see WCAG).

Also, you would still can&#039;t automatically mark text-only links, you would be doing that manually.</description>
		<content:encoded><![CDATA[<p>I&#8217;d rather not open links in a new window (and definitely not without warning the user &#8211; see WCAG).</p>
<p>Also, you would still can&#8217;t automatically mark text-only links, you would be doing that manually.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: debbie</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-59265</link>
		<dc:creator>debbie</dc:creator>
		<pubDate>Fri, 11 Jul 2008 05:53:35 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-59265</guid>
		<description>Hi... I&#039;m no CSS expert here, but I do have a suggestion. I noticed that when I blog using wordpress, the images I add do not have a target option. (‘_blank’, ‘_self’, ‘_top’ or ‘_parent’). For my usual text links, I always set it that it opens in a new window and therefore, I see ‘_blank’ in the link tag. 

Looks like this:

&lt;a href=&quot;#&quot; rel=&quot;nofollow&quot;&gt;Text&lt;/a&gt;

So maybe you could use this: 

a[target=&#039;_blank&#039;] {}

I know it doesn&#039;t solve the problem, but it&#039;s good enough for me anyway.

:)</description>
		<content:encoded><![CDATA[<p>Hi&#8230; I&#8217;m no CSS expert here, but I do have a suggestion. I noticed that when I blog using wordpress, the images I add do not have a target option. (‘_blank’, ‘_self’, ‘_top’ or ‘_parent’). For my usual text links, I always set it that it opens in a new window and therefore, I see ‘_blank’ in the link tag. </p>
<p>Looks like this:</p>
<p>&lt;a href=&#8221;#&#8221; rel=&#8221;nofollow&#8221;&gt;Text&lt;/a&gt;</p>
<p>So maybe you could use this: </p>
<p>a[target='_blank'] {}</p>
<p>I know it doesn&#8217;t solve the problem, but it&#8217;s good enough for me anyway.</p>
<p> <img src='http://alastairc.ac/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitri</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-47289</link>
		<dc:creator>Dmitri</dc:creator>
		<pubDate>Tue, 06 May 2008 15:37:07 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-47289</guid>
		<description>Not will work, or just apply a server side technology to mark the needed classes. Or place the A highlight first and then override it for specific elements such as img.

To the person who said + isnt yet used: its used for sibling selections.</description>
		<content:encoded><![CDATA[<p>Not will work, or just apply a server side technology to mark the needed classes. Or place the A highlight first and then override it for specific elements such as img.</p>
<p>To the person who said + isnt yet used: its used for sibling selections.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crumpetstilskin</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-34689</link>
		<dc:creator>Crumpetstilskin</dc:creator>
		<pubDate>Mon, 25 Feb 2008 23:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-34689</guid>
		<description>here from your early comment at the css3 standards suggest page. caveat: i am not a web type guy, so haven&#039;t followed much of the grotti obscuratia.

I have exactly the same desire as you  for usercontent control of &quot;text-node&quot; 

but in light of the ever-desired parent selector, wouldn&#039;t you also want to textnode style your inner=tag example: &lt;a href=&quot;#&quot;&gt;some &lt;strong&gt;other&lt;/strong&gt; text&lt;/a&gt;
??
if you don&#039;t want your inner &lt;strong&gt; to take on the textnode style, you can restyle it via accepted child selector:
a&gt;strong {blahhh:blahh;}
&lt;em&gt;[now hoping the this comment thingie takes encoding etc as intended]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>here from your early comment at the css3 standards suggest page. caveat: i am not a web type guy, so haven&#8217;t followed much of the grotti obscuratia.</p>
<p>I have exactly the same desire as you  for usercontent control of &#8220;text-node&#8221; </p>
<p>but in light of the ever-desired parent selector, wouldn&#8217;t you also want to textnode style your inner=tag example: &lt;a href=&#8221;#&#8221;&gt;some &lt;strong&gt;other&lt;/strong&gt; text&lt;/a&gt;<br />
??<br />
if you don&#8217;t want your inner &lt;strong&gt; to take on the textnode style, you can restyle it via accepted child selector:<br />
a&gt;strong {blahhh:blahh;}<br />
<em>[now hoping the this comment thingie takes encoding etc as intended]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Jordan</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-31280</link>
		<dc:creator>Lee Jordan</dc:creator>
		<pubDate>Tue, 29 Jan 2008 14:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-31280</guid>
		<description>I&#039;ve just run into this; wanting to back up the tree, whilst trying to figure out how to make expanding and contracting navigation without Javascript. Focus springs to mind but with a:focus the focus is triggered in an inconvenient place when it comes to cascading, my a doesn&#039;t contain the sub nav&#039;s but my li which lives above the a does. DOM is the only way.

But the CSS is hiding the sub nav items when the page loads so it should be able to traverse backwards from the A:focus to the LI sort of like:

li &lt;&lt; a:focus ul { display : block;}

This could say: Pass the focus from the a and re-cascade from the li downwards, even reading it as a human that makes sense as the direction is clearly shown.

Anyway without getting confused, cascading backwards while being really useful for navigation systems, is another buzzword or phrase to wow our peers with. &quot;Have you tried the reverse cascade trick?&quot;. If only we could do it for nav systems it would free use from JS.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just run into this; wanting to back up the tree, whilst trying to figure out how to make expanding and contracting navigation without Javascript. Focus springs to mind but with a:focus the focus is triggered in an inconvenient place when it comes to cascading, my a doesn&#8217;t contain the sub nav&#8217;s but my li which lives above the a does. DOM is the only way.</p>
<p>But the CSS is hiding the sub nav items when the page loads so it should be able to traverse backwards from the A:focus to the LI sort of like:</p>
<p>li &lt;&lt; a:focus ul { display : block;}</p>
<p>This could say: Pass the focus from the a and re-cascade from the li downwards, even reading it as a human that makes sense as the direction is clearly shown.</p>
<p>Anyway without getting confused, cascading backwards while being really useful for navigation systems, is another buzzword or phrase to wow our peers with. &#8220;Have you tried the reverse cascade trick?&#8221;. If only we could do it for nav systems it would free use from JS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-24284</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Wed, 31 Oct 2007 14:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-24284</guid>
		<description>Hi Simon,

I don&#039;t think that would work, I&#039;m trying to select the &#039;a&#039; element based on it&#039;s contents, not selecting the contents.

What you suggest would mean you&#039;re styling the contents, and that you would need an element within it (not just text).</description>
		<content:encoded><![CDATA[<p>Hi Simon,</p>
<p>I don&#8217;t think that would work, I&#8217;m trying to select the &#8216;a&#8217; element based on it&#8217;s contents, not selecting the contents.</p>
<p>What you suggest would mean you&#8217;re styling the contents, and that you would need an element within it (not just text).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-24267</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Wed, 31 Oct 2007 10:57:32 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-24267</guid>
		<description>I would argue that a pseudo class isn&#039;t the answer, as we are looking to select a node type in its own right, and which would then have its own set of pseudo classes.  What is needed is something more akin to the asterisk; pick a symbol that&#039;s not used yet, say &#039;+&#039;.  Then you can pick out the text node(s) within an element independently from images, etc., allowing (for instance):

&lt;code&gt;a &gt; +:first-child { ... }&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>I would argue that a pseudo class isn&#8217;t the answer, as we are looking to select a node type in its own right, and which would then have its own set of pseudo classes.  What is needed is something more akin to the asterisk; pick a symbol that&#8217;s not used yet, say &#8216;+&#8217;.  Then you can pick out the text node(s) within an element independently from images, etc., allowing (for instance):</p>
<p><code>a &gt; +:first-child { ... }</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-20216</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Sat, 11 Aug 2007 11:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-20216</guid>
		<description>From my reading of the current &lt;a href=&quot;http://www.w3.org/TR/css3-selectors/#negation&quot; rel=&quot;nofollow&quot;&gt;Negation sector&lt;/a&gt; spec (updated since this article), this:

&lt;code&gt;a *:not(img)&lt;/code&gt;

Would select any element inside a link that isn&#039;t an image. Which might work in your circumstances (e.g. if you have a &lt;code&gt;strong&lt;/code&gt; element inside the link), but not for me, because there is no other element inside the link, it&#039;s &lt;em&gt;just text&lt;/em&gt;. 

Therefore this won&#039;t be selected by your selector:

&lt;code&gt;&lt;a href=&#039;page.html&#039;&gt;example&lt;a&gt;&lt;/code&gt;

Conceptually, what we need is a variation of &lt;code&gt;E:empty&lt;/code&gt; that is for text nodes, e.g. &lt;code&gt;E:text&lt;/code&gt; or &lt;code&gt;E:no-children&lt;/code&gt;.</description>
		<content:encoded><![CDATA[<p>From my reading of the current <a href="http://www.w3.org/TR/css3-selectors/#negation" rel="nofollow">Negation sector</a> spec (updated since this article), this:</p>
<p><code>a *:not(img)</code></p>
<p>Would select any element inside a link that isn&#8217;t an image. Which might work in your circumstances (e.g. if you have a <code>strong</code> element inside the link), but not for me, because there is no other element inside the link, it&#8217;s <em>just text</em>. </p>
<p>Therefore this won&#8217;t be selected by your selector:</p>
<p><code>&lt;a href='page.html'&gt;example&lt;a&gt;</code></p>
<p>Conceptually, what we need is a variation of <code>E:empty</code> that is for text nodes, e.g. <code>E:text</code> or <code>E:no-children</code>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nux</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-20206</link>
		<dc:creator>Nux</dc:creator>
		<pubDate>Sat, 11 Aug 2007 05:05:56 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-20206</guid>
		<description>Wait... I got it!
:D

#contents a *:not(img) {
	color:black;
	text-decoration:none;
	border: 1px dotted #ccc;
}</description>
		<content:encoded><![CDATA[<p>Wait&#8230; I got it!<br />
 <img src='http://alastairc.ac/wordpress/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>#contents a *:not(img) {<br />
	color:black;<br />
	text-decoration:none;<br />
	border: 1px dotted #ccc;<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nux</title>
		<link>http://alastairc.ac/2006/10/text-nodes-and-css/comment-page-1/#comment-20205</link>
		<dc:creator>Nux</dc:creator>
		<pubDate>Sat, 11 Aug 2007 04:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/10/text-nodes-and-css/#comment-20205</guid>
		<description>I was hoping to find the exact same thing... Now at least I know it&#039;s not possible :(.</description>
		<content:encoded><![CDATA[<p>I was hoping to find the exact same thing&#8230; Now at least I know it&#8217;s not possible <img src='http://alastairc.ac/wordpress/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
</channel>
</rss>

