Re: [whatwg/webidl] Should we "check if we can run script" before calling callbacks? (#993)

sideshowbarker left a comment (whatwg/webidl#993)

FYI: After https://github.com/LadybirdBrowser/ladybird/pull/12697 is merged, Ladybird will be doing what Chrome and Firefox do; that is, Ladybird will refuse a callback whose realm’s global object is a `Window` whose associated `Document` isn’t fully active (and throw a `NotSupportedError`) when invoking a callback function, constructing one, and calling a user object’s operation.

Against the tentative tests in https://github.com/web-platform-tests/wpt/pull/63315, that takes Ladybird from 7/25 to 25/25 in `invoke.tentative.html`, from 3/9 to 9/9 in `construct.tentative.html`, and from 10/25 to 23/25 in `call-user-object-operation.tentative.html`.

The other 2 tests out of the 25 in `call-user-object-operation.tentative.html` are the `XPathNSResolver` cases in the fully active state, where Ladybird doesn’t call the resolver at all yet.

Promise jobs are unchanged: Like Safari, Ladybird still runs them for a navigated-away iframe, so 4 of the 13 subtests in `promise-jobs.tentative.html` fail.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/issues/993#issuecomment-6172234019
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/issues/993/6172234019@github.com>