- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 15 May 2017 21:47:54 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 16 May 2017 04:48:28 UTC
annevk commented on this pull request. > +<a>context object</a>'s [=AbortSignal/aborted flag=] is set, and false otherwise. + +<p class=note>Changes to an {{AbortSignal}} object represent the wishes of the corresponding +{{AbortController}} object, but an API observing the {{AbortSignal}} object can chose to ignore +them. For instance, if the operation has already completed. + +<p>To <dfn export for=AbortSignal>signal abort</dfn>, given a {{AbortSignal}} object +<var>signal</var>, run these steps: + +<ol> + <li><p>If <var>signal</var>'s [=AbortSignal/aborted flag=] is set, then return. + + <li><p>Set <var>signal</var>'s [=AbortSignal/aborted flag=]. + + <li><p><a for=set>For each</a> <var>algorithm</var> in <var>signal</var>'s + [=AbortSignal/abort algorithms=]: run <var>algorithm</var>. If we do that, we probably shouldn't allow adding new abort algorithms either if the aborted flag is set. Should we have a dedicated add algorithm folks can use? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/437#discussion_r116654273
Received on Tuesday, 16 May 2017 04:48:28 UTC