Fix null realm assertion when activating a service worker (#36256)

Ensure there is an active realm when dispatching the `activation` DOM
event to the ServiceWorker global.

Testing: Existing WPT coverage.
Fixes: #36114
Fixes: #36235
Fixes: #36231

Signed-off-by: Josh Matthews <josh@joshmatthews.net>
This commit is contained in:
Josh Matthews 2025-04-01 04:13:02 -04:00 committed by GitHub
parent be38c5478f
commit fcef1dff9d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
50 changed files with 579 additions and 116 deletions

View file

@ -1,2 +1,30 @@
[registration-script-module.https.html]
expected: CRASH
[Registering invalid chunked encoding script]
expected: FAIL
[Registering invalid chunked encoding script with flush]
expected: FAIL
[Registering script including parse error]
expected: FAIL
[Registering script including undefined error]
expected: FAIL
[Registering script including uncaught exception]
expected: FAIL
[Registering script with top-level await]
expected: FAIL
[Registering script with module instantiation error]
expected: FAIL
[Registering script with module instantiation error and top-level await]
expected: FAIL
[Registering non-existent script]
expected: FAIL
[Registering script including caught exception]
expected: FAIL