Re: [whatwg/fetch] Aborting fetch (#523)

> A readonly attribute shouldn't result in an exception. 

Why's that? FWIW the [web animation API](https://w3c.github.io/web-animations/#the-animation-interface) has a `.finished` property, the [font loading API](https://drafts.csswg.org/css-font-loading/#dom-fontface-loaded) has a `.loaded` property, and [streams](https://streams.spec.whatwg.org/#default-reader-closed) has a `.closed` property.

> @bakulf noted that the `Request` constructor doesn't seem to consistently create a new `AbortSignal` object. It sometimes just sets the signal to what is given. That seems wrong?

Yeah, that would be a bug, but I can't see it. `new Request()` always creates a new signal, and hooking up any provided signal happens in [step 31](https://fetch.spec.whatwg.org/branch-snapshots/cancelation/#dom-request).

-- 
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/fetch/pull/523#issuecomment-324264973