Skip to content

Conversation

@jakearchibald
Copy link
Contributor

@jakearchibald jakearchibald commented Sep 7, 2017

xhr.bs Outdated

<ul>
<li><p>Unset the <a><code>send()</code> flag</a>, <a>stop timeout flag</a>, and
<li><p>Unset the <a><code>send()</code> flag</a>, and
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for a comma anymore.

xhr.bs Outdated
<li><p>If <var>req</var>'s <a for=request>done flag</a> is unset, then
<a for=fetch>terminate</a> <a for=/>fetching</a> with reason <i>timeout</i>.
<li><p>If <var>req</var>'s <a for=request>done flag</a> is unset, then set the
<a>timed out flag</a>, and <a for=fetch>terminate</a> <a for=/>fetching</a>.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also no need for a comma here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the rule "use commas if there are more than two things to do"?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, or if it's needed because it would get unwieldy somehow.

xhr.bs Outdated
within the amount of milliseconds from the
{{XMLHttpRequest/timeout!!attribute}} attribute value with reason
<i>timeout</i>.
<p>If the {{XMLHttpRequest/timeout!!attribute}} attribute value is not zero, set the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

then set* if we're touching this

<i>timeout</i>.
<p>If the {{XMLHttpRequest/timeout!!attribute}} attribute value is not zero, set the
<a>timed out flag</a> and <a for=fetch>terminate</a> <a for=/>fetching</a> if it has not
returned within the amount of milliseconds from the {{XMLHttpRequest/timeout!!attribute}}.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should clarify what returned means here. But maybe as a follow-up since that's not your fault.

xhr.bs Outdated
<a for=fetch>terminate</a> the
<a for=/>fetch</a> algorithm operated by the
{{XMLHttpRequest}} object with reason <i>fatal</i>.
{{XMLHttpRequest}} object.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe inline this algorithm altogether at this point given you're removing 1 of the 3 callsites?

@annevk annevk requested a review from yutakahirano September 7, 2017 12:47
@annevk
Copy link
Member

annevk commented Sep 7, 2017

@yutakahirano could you please review this as well? Thanks!

xhr.bs Outdated
<a event><code>abort</code></a> and exception
<code>AbortError</code>.
<li>
<p>Otherwise, if <var>response</var>'s <a for=response>body</a>'s <a for=body>stream</a> has
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is errored

@annevk
Copy link
Member

annevk commented Sep 8, 2017

Proposed commit message:

Align with Fetch's upcoming abort revamp

See https://github.com/whatwg/fetch/pull/523 for details.

@jakearchibald
Copy link
Contributor Author

I'm happy with that.

@annevk annevk merged commit 1a8f691 into whatwg:master Sep 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants