http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/ All about WebKit development Mon, 12 May 2008 10:38:32 +0000 http://wordpress.org/?v=2.5.1 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24114 Robert Blaut Wed, 26 Mar 2008 20:55:38 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24114 Patrick, can you file a bug report about the issue to http://bugs.webkit.org? Patrick, can you file a bug report about the issue to http://bugs.webkit.org?

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24083 Somebee Wed, 26 Mar 2008 12:48:53 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24083 Have you fixed some other timing-bugs? I now consistently get 96/100, even after pagereload etc. In the last public build (which was supposed to get 95/100) I got everything from 90-95, different on each pageload. Keep up the _great_ work! Have you fixed some other timing-bugs? I now consistently get 96/100, even after pagereload etc. In the last public build (which was supposed to get 95/100) I got everything from 90-95, different on each pageload. Keep up the _great_ work!

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24081 Patrick Geiller Wed, 26 Mar 2008 11:36:11 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24081 Don't know if you've noticed, but the font smoothing of 'Acid3' differs between reference (subpixel) and test page (grayscale). Don’t know if you’ve noticed, but the font smoothing of ‘Acid3′ differs between reference (subpixel) and test page (grayscale).

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24080 aragost Wed, 26 Mar 2008 11:22:58 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24080 What about the upper right corner? Seems to me that there's more than a few pixel to fix there :) Well done however, keep up with the good work! What about the upper right corner? Seems to me that there’s more than a few pixel to fix there
Well done however, keep up with the good work!

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24078 solipsism Wed, 26 Mar 2008 09:47:01 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24078 I figure Apple will be very quick to get a stable update to Safari released so they can claim to be the first browser to be Acid3 compliant, and by a large margin. I figure Apple will be very quick to get a stable update to Safari released so they can claim to be the first browser to be Acid3 compliant, and by a large margin.

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24076 Mr.TFM Wed, 26 Mar 2008 09:42:52 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24076 And so, when webkit will reach 100%, we'll get Safari 3.2? And so, when webkit will reach 100%, we’ll get Safari 3.2?

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24072 solipsism Wed, 26 Mar 2008 03:02:21 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24072 There is certainly some difference with my browser and the thickness of the borders around the white box and the internal coloured boxes. Acid3 rendering with WebKit is slightly smaller than in the reference rendering. There is certainly some difference with my browser and the thickness of the borders around the white box and the internal coloured boxes. Acid3 rendering with WebKit is slightly smaller than in the reference rendering.

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24071 masterleep Wed, 26 Mar 2008 02:56:56 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24071 ah, i expected that the reference rendering was an image. Thanks for the explanation. ah, i expected that the reference rendering was an image. Thanks for the explanation.

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24070 Mark Rowe Wed, 26 Mar 2008 02:36:26 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24070 @masterleep: If you look at the <a href='http://acid3.acidtests.org/reference.html' rel="nofollow">reference rendering</a> of Acid 3 you'll notice that it is made up of a background image with the text positioned over top of it via CSS. By having the browser renders its own text for the reference rendering it is possible to expect that the test and reference match exactly. If the text were part of the reference image, then there would obviously be variance due to differing operating systems, font smoothing settings, and so forth. @masterleep: If you look at the reference rendering of Acid 3 you’ll notice that it is made up of a background image with the text positioned over top of it via CSS. By having the browser renders its own text for the reference rendering it is possible to expect that the test and reference match exactly. If the text were part of the reference image, then there would obviously be variance due to differing operating systems, font smoothing settings, and so forth.

]]> http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24069 masterleep Wed, 26 Mar 2008 02:33:31 +0000 http://webkit.org/blog/169/acid3-nodeiterator-fix-leaves-us-with-4-points-to-go/#comment-24069 when the test says that it must be pixel perfect, does that mean that font rendering is fully specified to the pixel? when the test says that it must be pixel perfect, does that mean that font rendering is fully specified to the pixel?

]]>