1
00:00:00,000 --> 00:00:05,020
Why did abort not stop my request?

2
00:00:05,020 --> 00:00:08,280
I created the controller.

3
00:00:08,280 --> 00:00:11,920
Apparently management by proximity was not enough.

4
00:00:12,100 --> 00:00:14,900
The request must receive the controller's signal.

5
00:00:14,900 --> 00:00:16,960
Calling abort then rejects that fetch.

6
00:00:16,960 --> 00:00:19,000
A controller next to a request

7
00:00:19,000 --> 00:00:19,820
has no effect on it.

8
00:00:20,000 --> 00:00:23,320
Catch cancellation separately from real failures.

9
00:00:23,320 --> 00:00:25,000
With the default abort reason,

10
00:00:25,000 --> 00:00:26,800
the error is named AbortError.

11
00:00:26,800 --> 00:00:28,400
Other failures still need reporting.

12
00:00:28,580 --> 00:00:32,920
For a deadline, fetch also accepts AbortSignal dot timeout.

13
00:00:32,920 --> 00:00:34,520
This example stops waiting after five

14
00:00:34,520 --> 00:00:37,020
seconds and needs timeout error handling too.

15
00:00:37,200 --> 00:00:41,560
Neither approach rolls back server work already performed.

16
00:00:41,560 --> 00:00:44,320
Use a new signal for a new attempt.

17
00:00:44,320 --> 00:00:46,640
Cancellation and undo are different contracts.

18
00:00:46,820 --> 00:00:49,600
The client left the meeting.

19
00:00:49,600 --> 00:00:51,580
The server is still making slides.