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,4 +1,18 @@
[dangling-markup-mitigation-allowed-apis.tentative.https.html]
expected: CRASH
[Does not block window.open(`resources/empty.html?\n<`,'_self')]
expected: FAIL
[Does not block xhr]
expected: FAIL
[Does not block EventSource]
expected: FAIL
[Does not block fetch]
expected: FAIL
[Does not block Worker]
expected: FAIL
[Does not block importScripts]
expected: FAIL

View file

@ -1,4 +1,4 @@
[dangling-markup-mitigation.tentative.https.html]
expected: CRASH
expected: ERROR
[Only blocks dangling markup requests]
expected: FAIL
expected: TIMEOUT