Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editorial: align with Fetch's change to tuples #7254

Merged
merged 4 commits into from
Oct 25, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 25 additions & 17 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -30702,8 +30702,8 @@ interface <dfn interface>HTMLIFrameElement</dfn> : <span>HTMLElement</span> {
<code>frame</code></span> given <var>element</var> and a new <span
data-x="concept-response">response</span> whose <span data-x="concept-response-url-list">URL
list</span> consists of <code>about:srcdoc</code>, <span
data-x="concept-response-header-list">header list</span> consists of `<code
data-x="">Content-Type</code>`/`<code>text/html</code>`, and <span
data-x="concept-response-header-list">header list</span> consists of (`<code
annevk marked this conversation as resolved.
Show resolved Hide resolved
data-x="">Content-Type</code>`, `<code>text/html</code>`), and <span
data-x="concept-response-body">body</span> is the value of <var>element</var>'s <code
data-x="attr-iframe-srcdoc">srcdoc</code> attribute.</p>

Expand Down Expand Up @@ -56854,8 +56854,8 @@ fur
<p><span>Plan to navigate</span> to a new <span data-x="concept-request">request</span> whose
<span data-x="concept-request-url">URL</span> is <var>parsed action</var>, <span
data-x="concept-request-method">method</span> is <var>method</var>, <span
data-x="concept-request-header-list">header list</span> consists of `<code
data-x="">Content-Type</code>`/<var>MIME type</var>, and <span
data-x="concept-request-header-list">header list</span> consists of (`<code
data-x="">Content-Type</code>`, <var>MIME type</var>), and <span
data-x="concept-request-body">body</span> is <var>body</var>.</p>
</dd>

Expand Down Expand Up @@ -87375,9 +87375,9 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
<p>If <span data-x="js-Type">Type</span>(<var>result</var>) is String, then set
<var>response</var> to a <span data-x="concept-response">response</span> whose <span
data-x="concept-response-header-list">header list</span> consists of
`<code>Content-Type</code>`/`<code data-x="">text/html;charset=utf-8</code>`, and whose <span
data-x="concept-response-body">body</span> is the result of <span data-x="UTF-8 encode">UTF-8
encoding</span> <var>result</var>.</p>
(`<code>Content-Type</code>`, `<code data-x="">text/html;charset=utf-8</code>`), and whose
<span data-x="concept-response-body">body</span> is the result of <span data-x="UTF-8
encode">UTF-8 encoding</span> <var>result</var>.</p>

<p class="note">The encoding to UTF-8 means that unpaired <span
data-x="surrogate">surrogates</span> will not roundtrip, once the HTML parser decodes the
Expand Down Expand Up @@ -98660,8 +98660,8 @@ dictionary <dfn dictionary>EventSourceInit</dfn> {
<li><p>Set <var>request</var>'s <span data-x="concept-request-client">client</span> to
<var>settings</var>.</p></li>

<li><p>User agents may <span data-x="concept-header-list-set">set</span> `<code
data-x="http-accept">Accept</code>`/`<code>text/event-stream</code>` in <var>request</var>'s
<li><p>User agents may <span data-x="concept-header-list-set">set</span> (`<code
data-x="http-accept">Accept</code>`, `<code>text/event-stream</code>`) in <var>request</var>'s
<span data-x="concept-request-header-list">header list</span>.</p></li>

<li><p>Set <var>request</var>'s <span data-x="concept-request-cache-mode">cache mode</span> to
Expand Down Expand Up @@ -98840,18 +98840,26 @@ dictionary <dfn dictionary>EventSourceInit</dfn> {
<ol>
<li><p>If the <code>EventSource</code> object's <code
data-x="dom-EventSource-readyState">readyState</code> attribute is not set to <code
data-x="dom-EventSource-CONNECTING">CONNECTING</code>, return.</p></li>
data-x="dom-EventSource-CONNECTING">CONNECTING</code>, then return.</p></li>

<li><p>Let <var>request</var> be the <code>EventSource</code> object's <span
data-x="concept-event-stream-request">request</span>.

<li><p>If the <code>EventSource</code> object's <span
data-x="concept-event-stream-last-event-id">last event ID string</span> is not the empty
string, <span data-x="concept-header-list-set">set</span> `<code
data-x="http-last-event-id">Last-Event-ID</code>`/<span
data-x="concept-event-stream-last-event-id">last event ID string</span>, <span data-x="UTF-8
encode">encoded as UTF-8</span>, in <var>request</var>'s <span
data-x="concept-request-header-list">header list</span>.</p></li>
<li>
<p>If the <code>EventSource</code> object's <span
data-x="concept-event-stream-last-event-id">last event ID string</span> is not the empty
string, then:</p>

<ol>
<li><p>Let <var>lastEventIDValue</var> be the <code>EventSource</code> object's <span
data-x="concept-event-stream-last-event-id">last event ID string</span>, <span data-x="UTF-8
encode">encoded as UTF-8</span>.</p></li>

<li><p><span data-x="concept-header-list-set">Set</span> (`<code
data-x="http-last-event-id">Last-Event-ID</code>`, <var>lastEventIDValue</var>) in
<var>request</var>'s <span data-x="concept-request-header-list">header list</span>.</p></li>
</ol>
</li>

<!--FETCH--><li><p><span data-x="concept-fetch">Fetch</span> <var>request</var> and process the
response obtained in this fashion, if any, as described earlier in this section.</p></li>
Expand Down