- From: Jake Archibald <notifications@github.com>
- Date: Fri, 09 Jun 2017 07:29:21 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 9 June 2017 14:29:54 UTC
I considered that, then thought it's easier to read if the abort steps are as close as possible to the thing being aborted.
As in:
1. Let abortSteps be the following sub steps and add them to signal:
1. …how to abort during task A…
1. Do task A.
1. Remove abortSteps from signal.
1. Set abortSteps to the following sub steps and add them to signal:
1. …how to abort during task B…
1. Do task B.
1. Remove abortSteps from signal.
Rather than:
To abort a fetch:
1. If currently performing task A:
1. …how to abort during task A…
1. Else if currently performing task B:
1. …how to abort during task B…
…then pages of scrolling away…
1. Do task A.
2. Do task B.
(I'm probably wrong here, just trying to figure out why)
--
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-307404328
Received on Friday, 9 June 2017 14:29:54 UTC