Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

I think the thing that's not adding up for me is that `.follow` seems to imply that the fetch being controlled will *adopt the state of the signal*, but there's also control that can put it *out of sync with the signal it's following* (including following a *second* signal). Like, I can't put my finger on it, but it feels like somewhere in this formulation is something relying on an assumption of consistency that's not guaranteed to be there.

-- 
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/issues/447#issuecomment-281761566