<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/link/2694891">
<title>Public marks on http://webkit.org/blog/158/the-acid-3-test/</title>
<description>Public marks on http://webkit.org/blog/158/the-acid-3-test/</description>
<link>http://blogmarks.net/marks/link/2694891</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1057732152"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1057725921"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1057732152">
<title>Surfin’ Safari - Blog Archive » The Acid 3 Test</title>
<link>http://webkit.org/blog/158/the-acid-3-test/</link>
<description>&lt;blockquote&gt;&lt;p&gt;WebKit had a number of minor parsing bugs that Acid 3 targeted. [...] We have updated our parser to be much closer to the HTML5-specified parsing rules.&lt;/p&gt;&lt;/blockquote&gt;

Moi qui croyait que le but d'Acid3 était de vérifier l'implémentation des standards.</description>
<dc:date>2008-03-13T00:12:47Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>Acid 3, html5, design by deficiency</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://webkit.org/blog/158/the-acid-3-test/"><img border="0" src="http://blogmarks.net/screenshots/2008/03/13/1f16aa04be454453d0b9862c150a9bd0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://webkit.org/blog/158/the-acid-3-test/">Surfin’ Safari - Blog Archive » The Acid 3 Test</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2694891">1 other(s)</a> 
<div class="description"><blockquote><p>WebKit had a number of minor parsing bugs that Acid 3 targeted. [...] We have updated our parser to be much closer to the HTML5-specified parsing rules.</p></blockquote>

Moi qui croyait que le but d'Acid3 était de vérifier l'implémentation des standards.</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Acid%2B3">Acid 3</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/design%2Bby%2Bdeficiency">design by deficiency</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057732152">Copy</a> | 
<a href="http://blogmarks.net/link/2694891">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1057725921">
<title>Surfin’ Safari - Blog Archive » The Acid 3 Test</title>
<link>http://webkit.org/blog/158/the-acid-3-test/</link>
<description>&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;WebKit has also never parsed DOCTYPEs before&lt;/strong&gt;. I re-wrote WebKit’s DOCTYPE parsing to match the HTML5 specification, and so now if you put a DOCTYPE into your page it will be present in the DOM. In addition many bugs centered around proper mode resolution (quirks vs. strict) have now been fixed. You can document.write a DOCTYPE for example in a new document and have the correct mode be selected.&lt;/p&gt;&lt;/blockquote&gt;

Just to illustrate how far browsers are (were) implementing previous specifications of html.</description>
<dc:date>2008-03-07T09:58:37Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>standards, w3c, html5, safari</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://webkit.org/blog/158/the-acid-3-test/"><img border="0" src="http://blogmarks.net/screenshots/2008/03/13/1f16aa04be454453d0b9862c150a9bd0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://webkit.org/blog/158/the-acid-3-test/">Surfin’ Safari - Blog Archive » The Acid 3 Test</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2694891">1 other(s)</a> 
<div class="description"><blockquote><p><strong>WebKit has also never parsed DOCTYPEs before</strong>. I re-wrote WebKit’s DOCTYPE parsing to match the HTML5 specification, and so now if you put a DOCTYPE into your page it will be present in the DOM. In addition many bugs centered around proper mode resolution (quirks vs. strict) have now been fixed. You can document.write a DOCTYPE for example in a new document and have the correct mode be selected.</p></blockquote>

Just to illustrate how far browsers are (were) implementing previous specifications of html.</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standards">standards</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/w3c">w3c</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/safari">safari</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057725921">Copy</a> | 
<a href="http://blogmarks.net/link/2694891">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>