From c747ce0c403d6d3172432a8ee089263db4d74578 Mon Sep 17 00:00:00 2001 From: Eriko Kurimoto Date: Fri, 13 Mar 2020 23:35:26 +0900 Subject: [PATCH] Fire an error event for parse errors when constructing SharedWorker This aligns the behavior of parse errors in a SharedWorker with fetch failures. See discussion in #5323, which has gone beyond that to also discuss other types of errors, but for now we have agreement on parse errors at least. --- source | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/source b/source index 3f73a2aa0c8..299d9e0558c 100644 --- a/source +++ b/source @@ -101577,13 +101577,17 @@ interface SharedWorkerGlobalScope : WorkerGlobalScope { fetch steps with response.

-

If the algorithm asynchronously completes with null, then:

+

If the algorithm asynchronously completes with null or with a script whose error to rethrow is non-null, then:

+
    -

  1. Queue a task to fire an event named - error at worker.

    2. -

  2. Run the environment discarding steps - for inside settings.

    3. -

  3. Return.

    4. +

  4. Queue a task to fire an event + named error at worker.

    5. + +

  5. Run the environment discarding steps + for inside settings.

    6. + +

  6. Return.

Otherwise, continue the rest of these steps after the algorithm's asynchronous completion,