<?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: Why? Why? Why?</title>
	<atom:link href="http://www.lauracowen.co.uk/blog/2006/07/08/why-why-why/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lauracowen.co.uk/blog/2006/07/08/why-why-why/</link>
	<description>Life, technology, research, and miscellany</description>
	<lastBuildDate>Mon, 26 Dec 2011 19:42:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Laura</title>
		<link>http://www.lauracowen.co.uk/blog/2006/07/08/why-why-why/comment-page-1/#comment-178</link>
		<dc:creator>Laura</dc:creator>
		<pubDate>Sun, 30 Jul 2006 17:08:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.lauracowen.co.uk/blog/2006/07/08/why-why-why/#comment-178</guid>
		<description>There *is* a standard at &lt;a title=&quot;w3c Web standards&quot; href=&quot;http://www.lauracowen.co.uk/blog/wp-admin/www.w3c.org&quot;&gt;W3C.org&lt;/a&gt;. &lt;a title=&quot;w3c CSS 1 specification&quot; href=&quot;http://www.w3.org/TR/CSS1&quot;&gt;Firefox legitimately supports the tag while IE legitimately doesn&#039;t.&lt;/a&gt;

The source of the page shows that the &lt;a rel=&quot;nofollow&quot; href=&quot;http://www.w3.org/TR/2005/WD-WCAG20-CSS-TECHS-20050630/Overview.html#text-decoration&quot;&gt;text-decoration:blink &lt;/a&gt; style has been added to each of the menu items. However, &lt;a title=&quot;Microsoft&#039;s MSDN site&quot; href=&quot;http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/textdecoration.asp&quot;&gt;Microsoft (legitimately and sensibly) don&#039;t render the blinking effect&lt;/a&gt;. The offending webpage, though, was created using Microsoft&#039;s FrontPage software, which I&#039;d expect to use IE under the covers, which doesn&#039;t display the blinking effect. I expect also that the site&#039;s designer, as Cerys says, tested the site in IE.

Maybe FrontPage does display the blinking, then when it didn&#039;t work in IE during testing, the designer just shrugged his/her shoulders and left the tag in. Who knows! I still blame the designer for poor taste, usability, and Accessibility.</description>
		<content:encoded><![CDATA[<p>There *is* a standard at <a title="w3c Web standards" href="http://www.lauracowen.co.uk/blog/wp-admin/www.w3c.org">W3C.org</a>. <a title="w3c CSS 1 specification" href="http://www.w3.org/TR/CSS1">Firefox legitimately supports the tag while IE legitimately doesn&#8217;t.</a></p>
<p>The source of the page shows that the <a rel="nofollow" href="http://www.w3.org/TR/2005/WD-WCAG20-CSS-TECHS-20050630/Overview.html#text-decoration">text-decoration:blink </a> style has been added to each of the menu items. However, <a title="Microsoft's MSDN site" href="http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/textdecoration.asp">Microsoft (legitimately and sensibly) don&#8217;t render the blinking effect</a>. The offending webpage, though, was created using Microsoft&#8217;s FrontPage software, which I&#8217;d expect to use IE under the covers, which doesn&#8217;t display the blinking effect. I expect also that the site&#8217;s designer, as Cerys says, tested the site in IE.</p>
<p>Maybe FrontPage does display the blinking, then when it didn&#8217;t work in IE during testing, the designer just shrugged his/her shoulders and left the tag in. Who knows! I still blame the designer for poor taste, usability, and Accessibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cerys</title>
		<link>http://www.lauracowen.co.uk/blog/2006/07/08/why-why-why/comment-page-1/#comment-110</link>
		<dc:creator>Cerys</dc:creator>
		<pubDate>Sun, 16 Jul 2006 09:08:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.lauracowen.co.uk/blog/2006/07/08/why-why-why/#comment-110</guid>
		<description>It works ok in Internet Explorer. To be honest with many sites I think you&#039;re lucky if they test it in anything but IE. Really though - isn&#039;t it about time that there was a standard that works in all of them anyway!</description>
		<content:encoded><![CDATA[<p>It works ok in Internet Explorer. To be honest with many sites I think you&#8217;re lucky if they test it in anything but IE. Really though &#8211; isn&#8217;t it about time that there was a standard that works in all of them anyway!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.lauracowen.co.uk/blog/2006/07/08/why-why-why/comment-page-1/#comment-81</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 09 Jul 2006 09:37:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.lauracowen.co.uk/blog/2006/07/08/why-why-why/#comment-81</guid>
		<description>I&#039;m not sure what you&#039;re talking about, I use a funny WebKit based browser on OS X which just shows a normal page. Lets put it into Firefox to check what it looks like there ... OMG!

For me though, sites like http://wildern.org/ are nearly as bad. Why the Flash ...why?</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure what you&#8217;re talking about, I use a funny WebKit based browser on OS X which just shows a normal page. Lets put it into Firefox to check what it looks like there &#8230; OMG!</p>
<p>For me though, sites like <a href="http://wildern.org/" rel="nofollow">http://wildern.org/</a> are nearly as bad. Why the Flash &#8230;why?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

