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,30 +1,8 @@
[service-worker-registration.https.html]
expected: CRASH
[Test: Asserts Installing Service Worker and its Registration]
[Test: Asserts Active Service Worker and its Registration]
expected: FAIL
[Test: Installing Service Worker ScriptURL property]
expected: FAIL
[Test: Throws Error when Invalid Scope]
expected: FAIL
[Test: Asserts Active Service Worker and its Registration]
expected: FAIL
[Test: Active Service Worker ScriptURL property]
expected: FAIL
[Test: Asserts ServiceWorkerContainer in Navigator]
expected: FAIL
[Test: Throws Error when Invalid Url Path]
expected: FAIL
[Test: Service Worker Registration property scope Url when no scope]
expected: FAIL
[Test: Service Worker Registration property scope when provided a scope]
[Test: Active Service Worker ScriptURL property]
expected: FAIL
[Test: Asserts Active Service Worker and its Registration]