Comments on: WebKit gets an A+ on Acid3 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/ All about WebKit development Sat, 17 May 2008 04:38:27 +0000 http://wordpress.org/?v=2.5.1 By: Maciej Stachowiak http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24033 Maciej Stachowiak Sun, 23 Mar 2008 21:25:21 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24033 @qazwart We have done a lot in 3.0 and 3.1 to improve support for editing toolkits. We've also worked with the vendors of rich text editing controls to help them improve their Safari code paths. The latest version of TinyMCE should work great, and WordPress will be updating to it soon. If you have specific bug reports on Confluence or Jira, please file them at http://bugs.webkit.org and we'll take a look! @qazwart We have done a lot in 3.0 and 3.1 to improve support for editing toolkits. We’ve also worked with the vendors of rich text editing controls to help them improve their Safari code paths. The latest version of TinyMCE should work great, and WordPress will be updating to it soon. If you have specific bug reports on Confluence or Jira, please file them at http://bugs.webkit.org and we’ll take a look!

]]> By: Mark Rowe http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24032 Mark Rowe Sun, 23 Mar 2008 20:07:30 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24032 Let me reiterate that the comments on blog posts are <i>not</i> an appropriate place to report bugs. We do not monitor all comments for reports of bugs, nor is it an appropriate medium for the back and forth that is often needed to isolate the issue. If you run into behaviour that you would consider a bug, please <a href='http://webkit.org/new-bug' rel="nofollow">file a bug report</a> via the proper channel. Let me reiterate that the comments on blog posts are not an appropriate place to report bugs. We do not monitor all comments for reports of bugs, nor is it an appropriate medium for the back and forth that is often needed to isolate the issue. If you run into behaviour that you would consider a bug, please file a bug report via the proper channel.

]]> By: Brad http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24030 Brad Sun, 23 Mar 2008 16:56:26 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24030 "So was that back in cobol and fortran times?" Not too far off. My HS had TRS-80s for the computer classes. “So was that back in cobol and fortran times?”

Not too far off. My HS had TRS-80s for the computer classes.

]]> By: Thomas Ganter http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24029 Thomas Ganter Sun, 23 Mar 2008 16:26:56 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24029 Probably I'm dumb, but my latest nightly, updated 10 minutes ago, consistently reaches 91/100. These tests fail: Failed 9 tests. Test 02 failed: reached expectation 13 when expecting expectation 12 Test 26 passed, but took 275ms Test 65 passed, but took 23ms Test 69 failed: Undefined value Test 70 failed: UTF-8 encoded XML document with invalid character did not have a well-formedness error Test 74 failed: getSVGDocument failed for referencing an svg document. Test 75 failed: Value undefined (result of expression anim.beginElement) is not object. Test 76 failed: expected '0' but got '100' - Incorrect animVal value after svg animation. Test 77 failed: expected '3' but got '0' - getNumberOfChars returned incorrect string length. Test 78 failed: expected '90' but got '0' - getRotationOfChar(0) failed. Test 79 failed: expected '34' but got '33' - SVGSVGTextElement.getNumberOfChars() incorrect Total elapsed time: 4.65s In case that matters: Leopard on PowerPC with Safari 3.1 in plain, new account, (i.e. all default settings). Probably I’m dumb, but my latest nightly, updated 10 minutes ago, consistently reaches 91/100.
These tests fail:

Failed 9 tests.
Test 02 failed: reached expectation 13 when expecting expectation 12
Test 26 passed, but took 275ms
Test 65 passed, but took 23ms
Test 69 failed: Undefined value
Test 70 failed: UTF-8 encoded XML document with invalid character did not have a well-formedness error
Test 74 failed: getSVGDocument failed for referencing an svg document.
Test 75 failed: Value undefined (result of expression anim.beginElement) is not object.
Test 76 failed: expected ‘0′ but got ‘100′ - Incorrect animVal value after svg animation.
Test 77 failed: expected ‘3′ but got ‘0′ - getNumberOfChars returned incorrect string length.
Test 78 failed: expected ‘90′ but got ‘0′ - getRotationOfChar(0) failed.
Test 79 failed: expected ‘34′ but got ‘33′ - SVGSVGTextElement.getNumberOfChars() incorrect
Total elapsed time: 4.65s

In case that matters:
Leopard on PowerPC with Safari 3.1 in plain, new account, (i.e. all default settings).

]]> By: DJCarbon43 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24027 DJCarbon43 Sun, 23 Mar 2008 14:34:42 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24027 @ Brad: LMAO, Nice :D So was that back in cobol and fortran times? ;) Happy Easter everyone! @ Brad: LMAO, Nice :D

So was that back in cobol and fortran times? ;)

Happy Easter everyone!

]]> By: qazwart http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24022 qazwart Sun, 23 Mar 2008 07:56:52 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24022 I'm glad Safari is doing so well against the Acid3 test. However, Safari has had problems with Midas/designMode support. I know that's not exactly standard, but its all over the web. Joomla, Mambo, anything that uses TinyMCE, Atlassian products (including Confluence), etc. I like Safari, but there are quite a few websites where I have to switch to FireFox in order to use them. I also know that Jira (Atlassian's bug tracking system) also has problems and it isn't related to Midas/designMode support. I don't know what it is, but I can't transition issues in Jira by simply clicking on them with Safari. I also notice that the latest WebKit breaks drop caps on one of my sites: http://etzahaim.org. It works in FireFox, Opera, IE, and even Safari 3.1. The latest WebKit breaks the drop cap. I'm submitting a bug on that one. I’m glad Safari is doing so well against the Acid3 test. However, Safari has had problems with Midas/designMode support. I know that’s not exactly standard, but its all over the web. Joomla, Mambo, anything that uses TinyMCE, Atlassian products (including Confluence), etc. I like Safari, but there are quite a few websites where I have to switch to FireFox in order to use them.

I also know that Jira (Atlassian’s bug tracking system) also has problems and it isn’t related to Midas/designMode support. I don’t know what it is, but I can’t transition issues in Jira by simply clicking on them with Safari.

I also notice that the latest WebKit breaks drop caps on one of my sites: http://etzahaim.org. It works in FireFox, Opera, IE, and even Safari 3.1. The latest WebKit breaks the drop cap. I’m submitting a bug on that one.

]]> By: wyuenho http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24021 wyuenho Sun, 23 Mar 2008 05:02:50 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24021 I don't why I test 69, 74, and 78 still consistently fail for me. This happens on Safari 3.1 and the nightlies. I'm on a iBook G4 (mid-2005) and on 10.4.11. Test 69 failed: Undefined value Test 74 failed: getSVGDocument failed for referencing an svg document. Test 78 failed: expected '90' but got '0' - getRotationOfChar(0) failed. This doesn't happen on Safari 3.1 windows and even on an Intel Mac running 10.4.11. This smells like platform specific enough to be a compiler optimization bug to me, but I'm just blind guessing. I don’t why I test 69, 74, and 78 still consistently fail for me. This happens on Safari 3.1 and the nightlies. I’m on a iBook G4 (mid-2005) and on 10.4.11.

Test 69 failed: Undefined value
Test 74 failed: getSVGDocument failed for referencing an svg document.
Test 78 failed: expected ‘90′ but got ‘0′ - getRotationOfChar(0) failed.

This doesn’t happen on Safari 3.1 windows and even on an Intel Mac running 10.4.11.

This smells like platform specific enough to be a compiler optimization bug to me, but I’m just blind guessing.

]]> By: masterleep http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24020 masterleep Sun, 23 Mar 2008 04:11:30 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24020 @Cameron Zwarich: I fixed that last night. See http://trac.webkit.org/projects/webkit/changeset/31228. Awesome, the team is obviously on top of things. Very impressive. @Cameron Zwarich: I fixed that last night. See http://trac.webkit.org/projects/webkit/changeset/31228.

Awesome, the team is obviously on top of things. Very impressive.

]]> By: Brad http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24019 Brad Sun, 23 Mar 2008 03:29:59 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24019 By the way, when I was in school, an A+ meant I did extra credit to rise above 100%. By the way, when I was in school, an A+ meant I did extra credit to rise above 100%.

]]> By: Brad http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24018 Brad Sun, 23 Mar 2008 03:28:15 +0000 http://webkit.org/blog/167/webkit-gets-an-a-on-acid3/#comment-24018 So 95% is an A+ and 100% is an A++? Good grief! Won't that make people who only get 90% sad? I think 90% should be A+,and there should be an extra plus for every percentage over 90. So Webkit gets an A++++++. Then we should award two pluses for every percentage over 95, so if anyone gets 100%, that would be A++++++++++++++++. To save space, we can write that as A16+. By the way, I still only get 91 (A++), with a big pause around 65 (B25–; there are no C's or D's). Maybe because I am on PowerPC? So 95% is an A+ and 100% is an A++? Good grief! Won’t that make people who only get 90% sad? I think 90% should be A+,and there should be an extra plus for every percentage over 90. So Webkit gets an A++++++. Then we should award two pluses for every percentage over 95, so if anyone gets 100%, that would be A++++++++++++++++. To save space, we can write that as A16+.

By the way, I still only get 91 (A++), with a big pause around 65 (B25–; there are no C’s or D’s). Maybe because I am on PowerPC?

]]>