From 0d097af1acbeabe56a1b0d0c2e2f521eca4defa8 Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Tue, 23 Jan 2018 15:24:34 +0100 Subject: [PATCH] Editorial: less continue after returning This fixes EventSource and WebSocket to follow a more accepted pattern for "in parallel". Fixes #692. --- source | 40 ++++++++++++++++++++++++---------------- 1 file changed, 24 insertions(+), 16 deletions(-) diff --git a/source b/source index 6d9a5fe18db..a2c9a70bd10 100644 --- a/source +++ b/source @@ -93848,10 +93848,14 @@ dictionary EventSourceInit {
  • Set ev's request to request.

  • -
  • Return ev, but continue these steps in parallel.

  • +
  • +

    Run this step in parallel:

    -
  • Fetch request.

  • +
      +
    1. Fetch request.

    2. +
    +
  • Return ev.


  • @@ -94689,24 +94693,28 @@ interface WebSocket : EventTarget { WebSocket protocol specification, then throw a "SyntaxError" DOMException.

    -
  • Return a new WebSocket object whose url is urlRecord, but continue these steps - in parallel.

  • -
  • -

    Establish a WebSocket connection given - urlRecord, protocols, and the entry settings object.

    +

    Run this step in parallel:

    + +
      +
    1. +

      Establish a WebSocket connection given + urlRecord, protocols, and the entry settings object.

      -

      If the establish a WebSocket - connection algorithm fails, it triggers the fail the - WebSocket connection algorithm, which then invokes the close the WebSocket connection algorithm, which then - establishes that the WebSocket connection is closed, - which fires the close event as - described below.

      +

      If the establish a WebSocket + connection algorithm fails, it triggers the fail the + WebSocket connection algorithm, which then invokes the close the WebSocket connection algorithm, which then + establishes that the WebSocket connection is closed, + which fires the close event as + described below.

      +
    2. +
  • +
  • Return a new WebSocket object whose url is urlRecord.