Bug 22604 – Add test to ensure that an onload handler named 'onload' is called properly

• Component: DOM
• Status: RESOLVED FIXED

[Pam Greene (IRC:pamg)]

Another test.

[Pam Greene (IRC:pamg)]

Created attachment 25684 [details]
New test + result

This test is not well suited to the JS wrapper because of the onload handler.

[Alexey Proskuryakov]

Is this the same as fast/dom/Element/onclick-case.html?

> This test is not well suited to the JS wrapper because of the onload handler.

It is also smaller and better because is doesn't use the JS wrapper - I don't think there's any reason at all to use js-test-pre and friends in this case.

[Darin Adler]

Comment on attachment 25684 [details]
New test + result

r=me

[Alexey Proskuryakov]

It still seems to me that this test doesn't check for anything that isn't already checked for by fast/dom/Element/onclick-case.html.

[Pam Greene (IRC:pamg)]

Only that onload isn't necessarily the same code path as onclick, demonstrated by the fact that at one point Chromium passed the onclick test but failed this one.

[Alexey Proskuryakov]

OK - this wasn't mentioned before, and the fix for onclick was totally generic.

[Pam Greene (IRC:pamg)]

Landed r39052

Right -- these tests are all part of the Chromium batch, so at some point Chromium passed everything else (that existed at the time) but failed this check.  Sorry for any confusion about that.