The offending div has auto margins, I guess the browsers are picking half pixel values. Although chromes element inspector shows the correct computed values, its acting like right and top are half a pixel less.
I've got the same chrome with both acid2 and its reference loaded in separate tabs so I can flick between them. The nose moves up and to the right by a tiny bit when flicking from the reference to the live render. Also there is a slightly darker yellow vertical line to the left of the nose that shouldn't be there indicating that the section containing the nose is shifted to the right by about half a pixel - which would explain the nose shifting right by about the same amount.
Do the chrome forks fix the chrome 6 beta rendering bugs. It fails the acid2 test (acid2.acidtests.org). Like firefox 4 beta 6 it draws the nose half a pixel too high, but then goes on to draw it half a pixel to the right. In addition chrome 6 beta has the eyes and their part of the face flick into the page only substantially later than the rest of the face. This test is supposed to be a static test with no dynamic content.
The parent comment sounds like argumentum ad hominem to me. Can we get a true scientist around here please... And, no, the irony of my comment is not lost on me.
decentralization = hard
The offending div has auto margins, I guess the browsers are picking half pixel values. Although chromes element inspector shows the correct computed values, its acting like right and top are half a pixel less.
I've got the same chrome with both acid2 and its reference loaded in separate tabs so I can flick between them. The nose moves up and to the right by a tiny bit when flicking from the reference to the live render. Also there is a slightly darker yellow vertical line to the left of the nose that shouldn't be there indicating that the section containing the nose is shifted to the right by about half a pixel - which would explain the nose shifting right by about the same amount.
Do the chrome forks fix the chrome 6 beta rendering bugs. It fails the acid2 test (acid2.acidtests.org). Like firefox 4 beta 6 it draws the nose half a pixel too high, but then goes on to draw it half a pixel to the right. In addition chrome 6 beta has the eyes and their part of the face flick into the page only substantially later than the rest of the face. This test is supposed to be a static test with no dynamic content.
The parent comment sounds like argumentum ad hominem to me. Can we get a true scientist around here please... And, no, the irony of my comment is not lost on me.
The acid2 test has the nose of the acid face half a pixel too high.