From 7fcb4ea5ba78b9d73f34e9c5077594f353c20858 Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Mon, 25 Oct 2021 17:54:08 +0200 Subject: [PATCH] Editorial: align with Fetch's change to tuples See https://github.com/whatwg/fetch/pull/1339 for context. --- source | 57 +++++++++++++++++++++++++++++++++------------------------ 1 file changed, 33 insertions(+), 24 deletions(-) diff --git a/source b/source index b991d35a02f..acdfa3123cb 100644 --- a/source +++ b/source @@ -2172,6 +2172,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • ASCII alpha
  • ASCII alphanumeric
  • isomorphic decode
    • +
  • isomorphic encode
  • ASCII lowercase
  • ASCII uppercase
  • ASCII case-insensitive
    • @@ -30701,9 +30702,9 @@ interface HTMLIFrameElement : HTMLElement {

    Navigate to the srcdoc resource: navigate an iframe or frame given element and a new response whose URL - list consists of about:srcdoc, header list consists of `Content-Type`/`text/html`, and is « about:srcdoc », header list is « (`Content-Type`, `text/html`) », and body is the value of element's srcdoc attribute.

    @@ -56818,7 +56819,7 @@ fur

    Set body to the result of encoding body.

    -

    Let MIME type be "application/x-www-form-urlencoded".

    +

    Let mimeType be `application/x-www-form-urlencoded`.

    multipart/form-data
    @@ -56828,11 +56829,11 @@ fur data-x="">multipart/form-data encoding algorithm with entry list and encoding.

    -

    Let MIME type be the concatenation of the string "multipart/form-data;", a U+0020 SPACE character, the string "boundary=", and the multipart/form-data - boundary string generated by the multipart/form-data - encoding algorithm.

    +

    Let mimeType be the isomorphic + encoding of the concatenation of "multipart/form-data; boundary=" and the multipart/form-data boundary string generated by the multipart/form-data encoding algorithm.

    text/plain
    @@ -56847,15 +56848,15 @@ fur

    Set body to the result of encoding body using encoding.

    -

    Let MIME type be "text/plain".

    +

    Let mimeType be `text/plain`.

    Plan to navigate to a new request whose URL is parsed action, method is method, header list consists of `Content-Type`/MIME type, and header list is « (`Content-Type`, mimeType) », and body is body.

    @@ -87374,8 +87375,8 @@ interface Location { // but see also Type(result) is String, then set response to a response whose header list consists of - `Content-Type`/`text/html;charset=utf-8`, and whose header list is « (`Content-Type`, + `text/html;charset=utf-8`) », and whose body is the result of UTF-8 encoding result.

    @@ -98664,8 +98665,8 @@ dictionary EventSourceInit {

  • Set request's client to settings.

    • -

  • User agents may set `Accept`/`text/event-stream` in request's +

  • User agents may set (`Accept`, `text/event-stream`) in request's header list.

  • Set request's cache mode to @@ -98844,18 +98845,26 @@ dictionary EventSourceInit {

    1. If the EventSource object's readyState attribute is not set to CONNECTING, return.

      2. + data-x="dom-EventSource-CONNECTING">CONNECTING, then return.

    2. Let request be the EventSource object's request. -

    3. If the EventSource object's last event ID string is not the empty - string, set `Last-Event-ID`/last event ID string, encoded as UTF-8, in request's header list.

      4. +
    4. +

      If the EventSource object's last event ID string is not the empty + string, then:

      + +
        +

      1. Let lastEventIDValue be the EventSource object's last event ID string, encoded as UTF-8.

        2. + +

      2. Set (`Last-Event-ID`, lastEventIDValue) in + request's header list.

        3. +
      +

    5. Fetch request and process the response obtained in this fashion, if any, as described earlier in this section.