Re: [whatwg/fetch] Add abort reason to abort fetch (PR #1343)

I think in the case where serialization and deserialization succeed we shouldn't temper with `signal.reason` (i.e., it should be possible for it to be an "empty" object). But when they don't I think we have to temper with it in some form, so we might as well use "`AbortError`" `DOMException`. That seems better than "`DataCloneError`" `DOMException`. (I guess we should test an explicit "`DataCloneError`" `DOMException`, that ought to work. 😊)

I'm not sure about adding public APIs for serializing/transferring `Request`, but anything we do should be compatible with that happening at some point.

-- 
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/1343#issuecomment-956149156