There seems to be a bug the test framework used by the layout tests. Upon completion the setUpPage function overwrites itself when it really means to update setUpPageComplete. I'm not sure exactly what the consequences are but in any case it seems wrong.
Correction: not setUpPageComplete but setUpPageStatus.
Can you be more specific about this?
If you run dom/xhtml/level2/html/HTMLIFrameElement11.xhtml an exception is thrown at selfxhtml.js:715 and the actual test is never run. However, the test is still marked as passed for some reason.
Also, if you look at the code in HTMLIFrameElement11.js (or any of the others like it) I think it is pretty obvious that overwriting setUpPage is not the intended behavior.
Here are the results for this test, I don't see it marked as passed:
Message titleLink: assertEquals failed, actual , expected NIST DOM HTML Test - FRAME.
Sorry, I picked the wrong HTMLIFrameElement11 -- I meant dom/html/level2/html/HTMLIFrameElement11.html. In safari 3.0.3 I get
Value complete (result of expression setUpPage) is not object.
Oh, that's a bad bug - thanks for catching it!
Interestingly, this particular test starts to crash for me when corrected :-(. I'm going to see if this can be easily fixed.
Note that this is a potential problem for any test whose .js file was created from the same template, which I think is most of them.
Yes, there were several thousand instances of this problem.
Filed <http://www.w3.org/Bugs/Public/show_bug.cgi?id=5227>, so that this could be fixed upstream, too.
*** Bug 16494 has been marked as a duplicate of this bug. ***
The bug in w3c is marked as fixed. How can we down steam changes to WebKit?
(In reply to comment #9)
> *** Bug 16494 has been marked as a duplicate of this bug. ***
(In reply to comment #8)
> Yes, there were several thousand instances of this problem.
> Filed <http://www.w3.org/Bugs/Public/show_bug.cgi?id=5227>, so that this could
> be fixed upstream, too.
We need to fix bug 15707, which blocks this one.
Fix committed r41140...r41145.