<?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"
	>
<channel>
	<title>Comments on: No highlighting in searchhi</title>
	<atom:link href="http://www.kryogenix.org/days/2007/03/16/no-highlighting-in-searchhi/feed" rel="self" type="application/rss+xml" />
	<link>http://www.kryogenix.org/days/2007/03/16/no-highlighting-in-searchhi</link>
	<description>scratched tallies on the prison wall</description>
	<pubDate>Tue, 02 Dec 2008 19:55:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: sil</title>
		<link>http://www.kryogenix.org/days/2007/03/16/no-highlighting-in-searchhi#comment-71553</link>
		<dc:creator>sil</dc:creator>
		<pubDate>Fri, 16 Mar 2007 17:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.kryogenix.org/days/2007/03/16/no-highlighting-in-searchhi#comment-71553</guid>
		<description>holst: true enough. I could make the class be "infrastructure" (which clearly wouldn't want to be highlighted, as opposed to "content" which would), but it bespeaks a certain amount of hubris. Making it happen from JS would require people to add a load of code to the top of their pages, which would be deeply infuriating to non-coders.</description>
		<content:encoded><![CDATA[<p>holst: true enough. I could make the class be &#8220;infrastructure&#8221; (which clearly wouldn&#8217;t want to be highlighted, as opposed to &#8220;content&#8221; which would), but it bespeaks a certain amount of hubris. Making it happen from JS would require people to add a load of code to the top of their pages, which would be deeply infuriating to non-coders.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bruce</title>
		<link>http://www.kryogenix.org/days/2007/03/16/no-highlighting-in-searchhi#comment-71465</link>
		<dc:creator>bruce</dc:creator>
		<pubDate>Fri, 16 Mar 2007 17:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.kryogenix.org/days/2007/03/16/no-highlighting-in-searchhi#comment-71465</guid>
		<description>blimey. I was wishing for something like this only yesterday. I owe you a bevvy.</description>
		<content:encoded><![CDATA[<p>blimey. I was wishing for something like this only yesterday. I owe you a bevvy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: holst</title>
		<link>http://www.kryogenix.org/days/2007/03/16/no-highlighting-in-searchhi#comment-71406</link>
		<dc:creator>holst</dc:creator>
		<pubDate>Fri, 16 Mar 2007 16:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.kryogenix.org/days/2007/03/16/no-highlighting-in-searchhi#comment-71406</guid>
		<description>Well, while this on the surface seems like a good idea, I'd really prefer a solution where you would define it in the javascript. "nosearchhi" isn't really a good description of any element, and then it's only a tad better than inline js, in my opinion.

Maybe I should consider editing the script to a more unobtrusive use.

Anyway, searchhi is still a great and very useful script.</description>
		<content:encoded><![CDATA[<p>Well, while this on the surface seems like a good idea, I&#8217;d really prefer a solution where you would define it in the javascript. &#8220;nosearchhi&#8221; isn&#8217;t really a good description of any element, and then it&#8217;s only a tad better than inline js, in my opinion.</p>
<p>Maybe I should consider editing the script to a more unobtrusive use.</p>
<p>Anyway, searchhi is still a great and very useful script.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
