Closed
Bug 1395141
Opened 7 years ago
Closed 7 years ago
RequestInit.signal should be marked as optional AbortSignal
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla57
Tracking | Status | |
---|---|---|
firefox57 | --- | fixed |
People
(Reporter: baku, Assigned: baku)
References
Details
Attachments
(1 file)
3.55 KB,
patch
|
bkelly
:
review+
|
Details | Diff | Splinter Review |
The spec used to say that it had to be: dictionary RequestInit { ... AbortSignal signal; ... }
Assignee | ||
Comment 1•7 years ago
|
||
Attachment #8902679 -
Flags: review?(bkelly)
Comment 2•7 years ago
|
||
Comment on attachment 8902679 [details] [diff] [review]
abort_3.patch
Review of attachment 8902679 [details] [diff] [review]:
-----------------------------------------------------------------
The spec editor made this change in the proposed spec as well after we discussed the test failure with him. Thanks!
Attachment #8902679 -
Flags: review?(bkelly) → review+
Pushed by amarchesini@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/a8369cf48aeb
RequestInit dictionary must have AbortSignal as optional, r=bkelly
Comment 4•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox57:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
![]() |
||
Comment 5•7 years ago
|
||
Wait, is this about optionality or nullability? The member was optional before this change, and still is; what changed is that it's now nullable, right?
Comment 6•7 years ago
|
||
Correct. The intent is nullability.
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•