Comments on: Acid3 nearing completion http://www.webstandards.org/2008/02/05/acid3-nearing-completion/ Working together for standards Wed, 27 Mar 2013 12:19:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Guillermo Garcia http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-70984 Guillermo Garcia Fri, 25 Apr 2008 15:47:51 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-70984 Firefox 3 Beta 5 @ Ubuntu 8.04 : 71/100 (.98 sec) Firefox 3 Beta 5 @ Ubuntu 8.04 : 71/100 (.98 sec)

]]> By: Kyle http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-68705 Kyle Thu, 03 Apr 2008 05:07:06 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-68705 Firefox 3 beta 5 gets 71/100 linktest failed Firefox 3 beta 5 gets 71/100 linktest failed

]]> By: Davide http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-66288 Davide Thu, 27 Mar 2008 20:41:00 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-66288 Wow! Latest Webkit nightly build gets 100/100! Wow!
Latest Webkit nightly build gets 100/100!

]]> By: Jean C http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-65806 Jean C Wed, 26 Mar 2008 21:09:45 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-65806 51/100 with Orca Browser 1.0 RC3 53/100 with Kamelon 1.1.4 58/100 with Firefox 3 Beta 1 51/100 with Orca Browser 1.0 RC3
53/100 with Kamelon 1.1.4
58/100 with Firefox 3 Beta 1

]]> By: alcatholic http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-65426 alcatholic Wed, 26 Mar 2008 05:35:41 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-65426 Reposting from the first Acid3 posting: OS X.4.11 Latest Webkit Nightly Build (r31307) (with Safari 3.1 installed, but not used) now gets 96/100 Safari 3.1 gets 75/100 linktest failed 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.” Reposting from the first Acid3 posting:

OS X.4.11

Latest Webkit Nightly Build (r31307) (with Safari 3.1 installed, but not used) now gets 96/100

Safari 3.1 gets 75/100 linktest failed

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.”

]]> By: Someone http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-65122 Someone Mon, 24 Mar 2008 03:23:25 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-65122 though i did not trace too deep into the code, it seems in the step 0 (erasing the javascript requirement) you expect a indentation to appear as a text node, which is absolutely not correct and not standard behavior... the standard states clearly that white characters like line feeds and whitespaces/tabs used for indentations are ignored in the dom tree and thus a indentation should never appear as a text node between tags (btw this is a bug that firefox has for way too long and even before firefox in mozilla, and does not seem to get corrected forever, or they don't want to correct it, making us to put no indentation between tags where we want to use some dom functions like nextsibling), if you are expecting it you may want to re-read the w3c specifications and correct it then again i repeat i did not went too deep so i can be wrong about you expecting that blank text node, but sure it does look like that another thing i see not very well is the inclusion of svg, yes, it is standard but not something that all browser have by default, which is very very unfair, the tests should be done with technologies that every decent browser has by default, or at least warn about having the appropiate plugin before taking the test though i did not trace too deep into the code, it seems in the step 0 (erasing the javascript requirement) you expect a indentation to appear as a text node, which is absolutely not correct and not standard behavior… the standard states clearly that white characters like line feeds and whitespaces/tabs used for indentations are ignored in the dom tree and thus a indentation should never appear as a text node between tags (btw this is a bug that firefox has for way too long and even before firefox in mozilla, and does not seem to get corrected forever, or they don’t want to correct it, making us to put no indentation between tags where we want to use some dom functions like nextsibling), if you are expecting it you may want to re-read the w3c specifications and correct it

then again i repeat i did not went too deep so i can be wrong about you expecting that blank text node, but sure it does look like that

another thing i see not very well is the inclusion of svg, yes, it is standard but not something that all browser have by default, which is very very unfair, the tests should be done with technologies that every decent browser has by default, or at least warn about having the appropiate plugin before taking the test

]]> By: Paulo Ricardo http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-64975 Paulo Ricardo Sun, 23 Mar 2008 02:51:50 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-64975 Firefox 3.0b5pre 2008032204 nightly - 71/100 Unfortunately, Firefox 3.0 final don't will beat the 100/100 rank. It's expected for 3.x or 4.0. Firefox 3.0b5pre 2008032204 nightly – 71/100

Unfortunately, Firefox 3.0 final don’t will beat the 100/100 rank. It’s expected for 3.x or 4.0.

]]> By: Barney http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-63319 Barney Fri, 07 Mar 2008 12:09:47 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-63319 Sorry I have just run the test again with WebKit r30868 safari 3 beta and am now getting 90 on windows XP. Sorry I have just run the test again with WebKit r30868 safari 3 beta and am now getting 90 on windows XP.

]]> By: Barney http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-63316 Barney Fri, 07 Mar 2008 11:56:03 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-63316 WebKit r30868 safari 3 beta Windows XP 88 / 100 IE8 Beta 8.0.6001.17184 17 / 100 WebKit r30868 safari 3 beta
Windows XP

88 / 100

IE8 Beta 8.0.6001.17184

17 / 100

]]> By: Jayce http://www.webstandards.org/2008/02/05/acid3-nearing-completion/comment-page-1/#comment-63211 Jayce Thu, 06 Mar 2008 10:47:53 +0000 http://www.webstandards.org/2008/02/05/acid3-nearing-completion/#comment-63211 Webkit r30790 gives 90/100. Mac OS X 10.5.2 10 to go... \o/ Webkit r30790 gives 90/100.
Mac OS X 10.5.2

10 to go…
\o/

]]>