<?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: Google Chrome is frustrating me</title>
	<atom:link href="http://nickcowie.com/2008/google-chrome-is-frustrating-me/feed/" rel="self" type="application/rss+xml" />
	<link>http://nickcowie.com/2008/google-chrome-is-frustrating-me/</link>
	<description>Web standards, accessibility  and such like with a bias toward  Government web sites</description>
	<lastBuildDate>Mon, 21 May 2012 14:57:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tom</title>
		<link>http://nickcowie.com/2008/google-chrome-is-frustrating-me/comment-page-1/#comment-37473</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 13 Jan 2009 11:05:42 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=339#comment-37473</guid>
		<description>I also agree with what you are saying and would also like to point (not sure if this is a Windows issue or a Chrome issue?) that when you use the rotate or scale CSS3 transitions functions the quality is really poor (check out my site: www.idle-words.co.uk in chrome to see for yourself)

It would be nice to see the quality improved!</description>
		<content:encoded><![CDATA[<p>I also agree with what you are saying and would also like to point (not sure if this is a Windows issue or a Chrome issue?) that when you use the rotate or scale CSS3 transitions functions the quality is really poor (check out my site: <a href="http://www.idle-words.co.uk" rel="nofollow">http://www.idle-words.co.uk</a> in chrome to see for yourself)</p>
<p>It would be nice to see the quality improved!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Cowie &#187; Browsers I rather not support</title>
		<link>http://nickcowie.com/2008/google-chrome-is-frustrating-me/comment-page-1/#comment-37461</link>
		<dc:creator>Nick Cowie &#187; Browsers I rather not support</dc:creator>
		<pubDate>Sun, 11 Jan 2009 03:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=339#comment-37461</guid>
		<description>[...] too early and has not included recent improvements that other webkit browsers have. For example the problem with border-radius and box-shadow, lack of support for @font-face. In addition the Chrome renders type differently from all other [...]</description>
		<content:encoded><![CDATA[<p>[…] too early and has not included recent improvements that other webkit browsers have. For example the problem with border-radius and box-shadow, lack of support for @font-face. In addition the Chrome renders type differently from all other […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Hogan</title>
		<link>http://nickcowie.com/2008/google-chrome-is-frustrating-me/comment-page-1/#comment-37420</link>
		<dc:creator>Alan Hogan</dc:creator>
		<pubDate>Sun, 21 Dec 2008 09:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=339#comment-37420</guid>
		<description>This is indeed interesting. I agree 100% with what you are saying.  I have to say, I am curious why Google’s version of webkit has this bug, and I am disappointed this made it into their stable 1.0 release.

Any divergences from Safari’s rendering engine are highly unfortunate, since there is no way to test Chrome on Mac (or Linux).</description>
		<content:encoded><![CDATA[<p>This is indeed interesting. I agree 100% with what you are saying.  I have to say, I am curious why Google’s version of webkit has this bug, and I am disappointed this made it into their stable 1.0 release.</p>
<p>Any divergences from Safari’s rendering engine are highly unfortunate, since there is no way to test Chrome on Mac (or Linux).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

