Closed
Bug 1750298
Opened 2 years ago
Closed 2 years ago
Remove `forAuthorCode` workaround for Fetch and use ReadableStreamDefaultReadResult
Categories
(Core :: DOM: Streams, task, P3)
Core
DOM: Streams
Tracking
()
RESOLVED
FIXED
100 Branch
Tracking | Status | |
---|---|---|
firefox100 | --- | fixed |
People
(Reporter: mgaudet, Assigned: evilpie)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
Attachments
(1 file)
In Bug 1734873 we ended up adding the forAuthorCode
system to avoid getting trapped by Object.prototype.then
Evilpie kindly pointed out that a more architecturally sound answer would be to instead use a separate type of ReadRequest for fetch code; which makes perfect sense in hindsight and should definitely be something we do.
Assignee | ||
Comment 1•2 years ago
|
||
Depends on D137382
Assignee | ||
Comment 2•2 years ago
|
||
This is changing some rather complex code in the FetchStreamReader
so I would like to avoid potentially spoiling the initial landing of DOM streams by delaying this for a few days.
Assignee | ||
Updated•2 years ago
|
Summary: Remove `forAuthorCode` workaround for Fetch → Remove `forAuthorCode` workaround for Fetch and use ReadableStreamDefaultReadResult
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → evilpies
Updated•2 years ago
|
Attachment #9261971 -
Attachment description: WIP: Bug 1750298 - Use custom ReadRequest for FetchStreamReader → Bug 1750298 - Use custom ReadRequest for FetchStreamReader
Updated•2 years ago
|
Attachment #9261971 -
Attachment description: Bug 1750298 - Use custom ReadRequest for FetchStreamReader → WIP: Bug 1750298 - Use custom ReadRequest for FetchStreamReader
Updated•2 years ago
|
Attachment #9261971 -
Attachment description: WIP: Bug 1750298 - Use custom ReadRequest for FetchStreamReader → Bug 1750298 - Use custom ReadRequest for FetchStreamReader. r?smaug!,mgaudet
Pushed by evilpies@gmail.com: https://hg.mozilla.org/integration/autoland/rev/4ec8f7211b07 Use custom ReadRequest for FetchStreamReader. r=smaug
Comment 5•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•