<?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: Will Google Chrome play havoc on Web Agencies?</title>
	<atom:link href="http://www.heavychef.com/will-google-chrome-play-havoc-on-web-agencies/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.heavychef.com/will-google-chrome-play-havoc-on-web-agencies/</link>
	<description>Practical Learning About Digital Marketing</description>
	<lastBuildDate>Sun, 05 Feb 2012 04:11:42 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew Smith</title>
		<link>http://www.heavychef.com/will-google-chrome-play-havoc-on-web-agencies/comment-page-1/#comment-448</link>
		<dc:creator>Andrew Smith</dc:creator>
		<pubDate>Wed, 03 Sep 2008 19:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.heavychef.com/?p=635#comment-448</guid>
		<description>I had exactly the same thought, but then I heard that Chrome is based on Webkit, which is the rendering engine of Safari. I&#039;ve always wanted our sites to be compatible with Safari, but I never bothered because testing was a bit of a pain (although the Safari for Windows helped). Now it will seem worth it to kill 2 birds with one stone.
Safari should be a big winner out of this, because their engine will improve as Google improves Webkit, plus more developers will indirectly make their sites will work in Safari, which makes Safari appear like a better browser.</description>
		<content:encoded><![CDATA[<p>I had exactly the same thought, but then I heard that Chrome is based on Webkit, which is the rendering engine of Safari. I&#8217;ve always wanted our sites to be compatible with Safari, but I never bothered because testing was a bit of a pain (although the Safari for Windows helped). Now it will seem worth it to kill 2 birds with one stone.<br />
Safari should be a big winner out of this, because their engine will improve as Google improves Webkit, plus more developers will indirectly make their sites will work in Safari, which makes Safari appear like a better browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.heavychef.com/will-google-chrome-play-havoc-on-web-agencies/comment-page-1/#comment-446</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Tue, 02 Sep 2008 22:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.heavychef.com/?p=635#comment-446</guid>
		<description>Wow.</description>
		<content:encoded><![CDATA[<p>Wow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Beech</title>
		<link>http://www.heavychef.com/will-google-chrome-play-havoc-on-web-agencies/comment-page-1/#comment-447</link>
		<dc:creator>Chris Beech</dc:creator>
		<pubDate>Tue, 02 Sep 2008 19:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.heavychef.com/?p=635#comment-447</guid>
		<description>what i find really interesting is that Google is using their own massive infrastructure to test chrome in terms of rendering web pages.

From Techcrunch: &quot;The company is claiming that its Chrome Bot can test the browser on tens of thousands of different webpages within 20-30 minutes of each build. These webpages are chosen on the basis of their popularity, which has already been determined by Google with the data it collects from its search users. When Google started testing Chrome, it only rendered 23% of those pages correctly (now it apparently renders 99% correctly).&quot;

That&#039;s great news for web developers!</description>
		<content:encoded><![CDATA[<p>what i find really interesting is that Google is using their own massive infrastructure to test chrome in terms of rendering web pages.</p>
<p>From Techcrunch: &#8220;The company is claiming that its Chrome Bot can test the browser on tens of thousands of different webpages within 20-30 minutes of each build. These webpages are chosen on the basis of their popularity, which has already been determined by Google with the data it collects from its search users. When Google started testing Chrome, it only rendered 23% of those pages correctly (now it apparently renders 99% correctly).&#8221;</p>
<p>That&#8217;s great news for web developers!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

