Closed Bug 377295 Opened 17 years ago Closed 17 years ago

Mochikit test for bug 366770 fails for me, because constructor can be run after onload

Categories

(Core :: XBL, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla1.9alpha5

People

(Reporter: martijn.martijn, Assigned: Gavin)

References

()

Details

(Keywords: testcase)

Attachments

(2 files)

Attached file testcase
See testcase, it alerts 'undefined' for me, but the way the mochikit test is made, it expects 'true' as the outcome for the alert.
The mochikit test should not expect that the constructor has been run after onload of the document.
Attached patch patchSplinter Review
Moves the finish() call into the constructor.
Assignee: nobody → gavin.sharp
Status: NEW → ASSIGNED
Attachment #263173 - Flags: review?(martijn.martijn)
OS: Windows XP → All
Priority: -- → P3
Hardware: PC → All
Target Milestone: --- → mozilla1.9alpha5
Comment on attachment 263173 [details] [diff] [review]
patch

Ok, thanks, that seems right to me.
Attachment #263173 - Flags: review?(martijn.martijn) → review+
mozilla/content/xbl/test/test_bug366770.html 	1.2
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Is there a bug on the underlying problem here?  Constructor execution should perhaps block onload...
Flags: in-testsuite+
Component: Testing → XBL
QA Contact: testing → xbl
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: