Thanks for writing these cases by LC exit. It really makes the process of providing feedback prior to CR a lot easier. I ran these (the tests below fail on Safari3 ,Firefox 3 and IE8) with my team and had a few questions. If these issues can be addressed we can give further feedback and recommendations on the results/implementations. (Let me know if I’m wrong on our test analysis!) The rest of the tests that fail (without issues in the test itself) are being investigated further by my team so expect more over the next few days as we dig in.
Microsoft Way, Redmond WA 98052
FAX# (425) 936-7329
On Fri, 06 Jun 2008 04:47:31 +0200, Sunava Dutta
<[hidden email]> wrote:
> Meanwhile, I'd like to re-iterate a point I had raised up awhile back.
> Are the tests going to be 'complete' /comprehensive at CR in relation to
> the spec? MSFT obviously wants this test suite to be official ensuring
> that third parties do not write individual test cases undermining the
> credibility of the suite and demonstrating increased/decreased
> compliance post CR (when it's much harder to make changes).
The test suite will be made complete (and "official") during the CR period
as per W3C policy. (And is required to be complete before we can exit CR.)
Anne van Kesteren
In reply to this post by Sunava Dutta
To add to the list:
- expects exceptions to be thrown when the spec has been updated to return null/""
- test assumes bad value will be ignored instead of throwing
I also had a question about the complex/001.htm test case. This test case seems to imply that readystatechange listeners are ordered. However, this is not specified in the XHR spec. The DOM Events spec explicitly says that listeners may be triggered in any order. It seems that all major browsers do actually keep the listeners ordered, and I've run across at least one webpage that relies on this behavior, but I don't think it's good form for a W3C test to be relying on it.
* Kartikaya Gupta wrote:
>I also had a question about the complex/001.htm test case. This test
>case seems to imply that readystatechange listeners are ordered.
>However, this is not specified in the XHR spec. The DOM Events spec
>explicitly says that listeners may be triggered in any order. It seems
>that all major browsers do actually keep the listeners ordered, and I've
>run across at least one webpage that relies on this behavior, but I
>don't think it's good form for a W3C test to be relying on it.
The triggering order is undefined in DOM Level 2 Events, but defined in
DOM Level 3 Events.
Björn Höhrmann · mailto:[hidden email] · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
|Free forum by Nabble||Edit this page|