- From: Ron Buckton <notifications@github.com>
- Date: Wed, 12 Apr 2017 16:24:37 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 April 2017 23:25:10 UTC
rbuckton commented on this pull request. > + }); + } + </pre> + + APIs that require more granular control could extend both {{AbortController}} and {{AbortSignal}} + according to their needs. +</div> + +<h3 id=interface-abortcontroller>Interface {{AbortController}}</h3> + +<pre class="idl"> +[Constructor(), Exposed=(Window,Worker)] +interface AbortController { + [SameObject] readonly attribute AbortSignal signal; + + void abort(); @jyasskin The result of `cancel()` in prex is to observe any errors thrown in the registered callback (or here, the onabort event), and respond accordingly. In prex, registered callbacks are not evaluated immediately and as a result the only way to observe the exception is through a Promise. A Promise return wouldn't strictly be necessary if `cancel()` ran to completion synchronously. -- 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_r111282310
Received on Wednesday, 12 April 2017 23:25:10 UTC