Re: [html-tests] Add tests for the realms involved in compiling event handlers (#4988)

> foo.html resolves to a 404 page, which fires the onload just fine...

I guess I'm not sure why both Chrome and Firefox time out on that test, then, per test results above.

> Why did you think return value conversion was relevant to the incumbent global?

Because when the return value conversion is happening the incumbent global is whatever was pushed for the callback.

So this test is testing the incumbent global that gets stored when window.onbeforeunload is assigned, but that has nothing to do with event handler compilation.

You may want to leave that test and add one which does:

    <body onbeforeunload="return { toString: etc }">

to test the incumbent set up with event handler compilation.

View on GitHub: https://github.com/w3c/web-platform-tests/pull/4988#issuecomment-282043100

Received on Thursday, 23 February 2017 16:27:46 UTC