-
Notifications
You must be signed in to change notification settings - Fork 133
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
Updating to fit with fetch aborting #152
Conversation
xhr.bs
Outdated
@@ -526,7 +524,7 @@ methods, when invoked, must run these steps: | |||
<p>Set variables associated with the object as follows: | |||
|
|||
<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 |
There was a problem hiding this comment.
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>. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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"?
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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
xhr.bs
Outdated
<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}}. |
There was a problem hiding this comment.
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
@@ -418,7 +416,7 @@ turn causes the <a>use-CORS-preflight flag</a> to be set.) | |||
<p>To <dfn>terminate the request</dfn>, | |||
<a for=fetch>terminate</a> the | |||
<a for=/>fetch</a> algorithm operated by the | |||
{{XMLHttpRequest}} object with reason <i>fatal</i>. | |||
{{XMLHttpRequest}} object. |
There was a problem hiding this comment.
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?
@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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is errored
Proposed commit message:
|
I'm happy with that. |
Preview | Diff