Remove NativeUnderlyingSource
Categories
(Core :: DOM: Streams, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox98 | --- | fixed |
People
(Reporter: evilpie, Assigned: evilpie)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Everything is specialized for BodyStream
anyway, so this base class is superfluous.
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
I thought the idea was that NativeUnderlyingSource will be used by other users in the near future.
Comment 3•3 years ago
|
||
In theory, yes. In practice, it's insufficiently well proven to support that use right now, and I would rather someone trying to make a new consumer here not be confused into thinking that this is just going to work because it really might not; step one for trying to add a new consumer may well be to revert this removal, but I'm very supportive of removing this until the story is clearer.
Comment 5•3 years ago
|
||
Jan, you may want to take a look at this change. I assume we'll need something like NativeUnderlyingSource for OPFS.
Comment 6•3 years ago
|
||
Hard to say at this point, we are currently implementing only basic functionality of OPFS. I will know more once we get to implementing stream support.
Anyway, thanks for letting me know.
Comment 7•3 years ago
|
||
bugherder |
Description
•