<?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: Acid3: Putting Browser Makers on Notice, Again.</title>
	<atom:link href="http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/</link>
	<description>Working together for standards</description>
	<lastBuildDate>Wed, 27 Mar 2013 12:19:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Marte</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-71294</link>
		<dc:creator>Marte</dc:creator>
		<pubDate>Thu, 15 May 2008 01:43:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-71294</guid>
		<description>Epiphany 2.22.1.1, which uses Webkit as the rendering engine, completely pass the test.</description>
		<content:encoded><![CDATA[<p>Epiphany 2.22.1.1, which uses Webkit as the rendering engine, completely pass the test.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Resimler</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-70566</link>
		<dc:creator>Resimler</dc:creator>
		<pubDate>Thu, 10 Apr 2008 17:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-70566</guid>
		<description>I like this post.Hopefully they pass Acid 3 by the FF3 release.</description>
		<content:encoded><![CDATA[<p>I like this post.Hopefully they pass Acid 3 by the FF3 release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Orso</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-70556</link>
		<dc:creator>Robert Orso</dc:creator>
		<pubDate>Thu, 10 Apr 2008 11:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-70556</guid>
		<description>I&#039;m not convinced that Mozilla will get a 100/100 score in the next couple of years. While the Gecko-Engine improves from version to version, the ACID3 test checks, among others, the correct implementation of &quot;CSS2 (@font-face)&quot;.

This includes the support of the &quot;src&quot; parameter to specify a dynamically loadable font-file.

You did note that this is a CSS2 feature, did you? A specification that dates back to 1998.

As Netscape released the Source of the browser back in 1998, the community had to remove the support for dynamically loaded fonts due to copyright-issues. It&#039;s a long lasting and unresolved bug (https://bugzilla.mozilla.org/show_bug.cgi?id=52746, https://bugzilla.mozilla.org/show_bug.cgi?id=70132) with no hint of progress in the mean time.

The licenses of the font vendors obviously require a &quot;closed source&quot; implementation and the Mozilla license obviously prohibits just that - the utilisation of a closed source library. A classical deadlock.

We had the 10th aniversary of this unfortune happening lately.

Maybe the OpenType specification and a set of public domain fonts can solve this issue one day.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not convinced that Mozilla will get a 100/100 score in the next couple of years. While the Gecko-Engine improves from version to version, the ACID3 test checks, among others, the correct implementation of &#8220;CSS2 (@font-face)&#8221;.</p>
<p>This includes the support of the &#8220;src&#8221; parameter to specify a dynamically loadable font-file.</p>
<p>You did note that this is a CSS2 feature, did you? A specification that dates back to 1998.</p>
<p>As Netscape released the Source of the browser back in 1998, the community had to remove the support for dynamically loaded fonts due to copyright-issues. It&#8217;s a long lasting and unresolved bug (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=52746" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=52746</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=70132" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=70132</a>) with no hint of progress in the mean time.</p>
<p>The licenses of the font vendors obviously require a &#8220;closed source&#8221; implementation and the Mozilla license obviously prohibits just that &#8211; the utilisation of a closed source library. A classical deadlock.</p>
<p>We had the 10th aniversary of this unfortune happening lately.</p>
<p>Maybe the OpenType specification and a set of public domain fonts can solve this issue one day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tristan Young</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-68648</link>
		<dc:creator>Tristan Young</dc:creator>
		<pubDate>Wed, 02 Apr 2008 20:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-68648</guid>
		<description>Firefox 3 Beta 5 scores 71/100 on ACID3, which is better than Beta 4, which was 67 if memory serves me.

I was hoping to see the various squares turn different colors, rather than shades of gray.  I hope this will be fixed in time for the official release.

There are also a few artifacts (2 small red squares, white X against a magenta background).

I&#039;m glad to see improvements being made.  It&#039;s only a matter of time.</description>
		<content:encoded><![CDATA[<p>Firefox 3 Beta 5 scores 71/100 on ACID3, which is better than Beta 4, which was 67 if memory serves me.</p>
<p>I was hoping to see the various squares turn different colors, rather than shades of gray.  I hope this will be fixed in time for the official release.</p>
<p>There are also a few artifacts (2 small red squares, white X against a magenta background).</p>
<p>I&#8217;m glad to see improvements being made.  It&#8217;s only a matter of time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ethana2</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-68123</link>
		<dc:creator>ethana2</dc:creator>
		<pubDate>Tue, 01 Apr 2008 11:17:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-68123</guid>
		<description>Firefox3 beta5 comes out soon!  I can&#039;t wait to see what it scores...

Here&#039;s hoping for a firefox 3.0 release that passes acid3 completely!</description>
		<content:encoded><![CDATA[<p>Firefox3 beta5 comes out soon!  I can&#8217;t wait to see what it scores&#8230;</p>
<p>Here&#8217;s hoping for a firefox 3.0 release that passes acid3 completely!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alcatholic</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-65908</link>
		<dc:creator>alcatholic</dc:creator>
		<pubDate>Thu, 27 Mar 2008 03:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-65908</guid>
		<description>Congrats to Opera!

Webkit also just made 100/100, and there is a stable, public release.

http://webkit.org/blog/173/webkit-achieves-acid3-100100-in-public-build/

Congrats to the Webkit crew!</description>
		<content:encoded><![CDATA[<p>Congrats to Opera!</p>
<p>Webkit also just made 100/100, and there is a stable, public release.</p>
<p><a href="http://webkit.org/blog/173/webkit-achieves-acid3-100100-in-public-build/" rel="nofollow">http://webkit.org/blog/173/webkit-achieves-acid3-100100-in-public-build/</a></p>
<p>Congrats to the Webkit crew!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fernando</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-65867</link>
		<dc:creator>Fernando</dc:creator>
		<pubDate>Thu, 27 Mar 2008 00:44:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-65867</guid>
		<description>Opera Rocks!!!!

THE FIRST ONE THAT PASSES THE ACID3 TEST
http://my.opera.com/desktopteam/blog/2008/03/26/opera-and-the-acid3-test</description>
		<content:encoded><![CDATA[<p>Opera Rocks!!!!</p>
<p>THE FIRST ONE THAT PASSES THE ACID3 TEST<br />
<a href="http://my.opera.com/desktopteam/blog/2008/03/26/opera-and-the-acid3-test" rel="nofollow">http://my.opera.com/desktopteam/blog/2008/03/26/opera-and-the-acid3-test</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DWalla</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-65861</link>
		<dc:creator>DWalla</dc:creator>
		<pubDate>Thu, 27 Mar 2008 00:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-65861</guid>
		<description>Apple&#039;s current nightly WebKit build is now at 98/100 on the Acid3 test.</description>
		<content:encoded><![CDATA[<p>Apple&#8217;s current nightly WebKit build is now at 98/100 on the Acid3 test.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nao</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-65778</link>
		<dc:creator>Nao</dc:creator>
		<pubDate>Wed, 26 Mar 2008 19:40:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-65778</guid>
		<description>Looks like Opera is officially the first to pass the test ;)
http://my.opera.com/desktopteam/blog/2008/03/26/opera-and-the-acid3-test</description>
		<content:encoded><![CDATA[<p>Looks like Opera is officially the first to pass the test ;)<br />
<a href="http://my.opera.com/desktopteam/blog/2008/03/26/opera-and-the-acid3-test" rel="nofollow">http://my.opera.com/desktopteam/blog/2008/03/26/opera-and-the-acid3-test</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alcatholic</title>
		<link>http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/comment-page-1/#comment-65427</link>
		<dc:creator>alcatholic</dc:creator>
		<pubDate>Wed, 26 Mar 2008 05:50:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2008/03/03/acid3-putting-browser-makers-on-notice-again/#comment-65427</guid>
		<description>Reposting:

OS X.4.11

Webkit Nightly Build (r31307) (with Safari 3.1 installed, but not used) now gets 96/100

They’ve also just introduced an optimization into Webkit nightlies for pageloading that is very sweet on script heavy pages.
http://webkit.org/blog/166/optimizing-page-loading-in-web-browser/

“The latest WebKit nightlies contain some new optimizations to reduce the impact of network latency. When script loading halts the main parser, we start up a side parser that goes through the rest of the HTML source to find more resources to load. We also prioritize resources so that scripts and stylesheets load before images. The overall effect is that we are now able to load more resources in parallel with scripts, including other scripts.”</description>
		<content:encoded><![CDATA[<p>Reposting:</p>
<p>OS X.4.11</p>
<p>Webkit Nightly Build (r31307) (with Safari 3.1 installed, but not used) now gets 96/100</p>
<p>They’ve also just introduced an optimization into Webkit nightlies for pageloading that is very sweet on script heavy pages.<br />
<a href="http://webkit.org/blog/166/optimizing-page-loading-in-web-browser/" rel="nofollow">http://webkit.org/blog/166/optimizing-page-loading-in-web-browser/</a></p>
<p>“The latest WebKit nightlies contain some new optimizations to reduce the impact of network latency. When script loading halts the main parser, we start up a side parser that goes through the rest of the HTML source to find more resources to load. We also prioritize resources so that scripts and stylesheets load before images. The overall effect is that we are now able to load more resources in parallel with scripts, including other scripts.”</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.320 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-05-02 12:17:19 -->