Closed
Bug 1805135
Opened 3 years ago
Closed 3 years ago
FileSystemWritableFileStream should use the default writer for all IO operations
Categories
(Core :: DOM: File, task, P2)
Core
DOM: File
Tracking
()
RESOLVED
FIXED
110 Branch
Tracking | Status | |
---|---|---|
firefox110 | --- | fixed |
People
(Reporter: janv, Assigned: janv)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
FileSystemWritableFileStream::Write, FileSystemWritableFileStream::Seek and FileSystemWritableFileStream::Truncate currently bypass the default writer mechanism provided by the parent class/interface WritableFileStream. This can lead to ordering issues.
Assignee | ||
Comment 1•3 years ago
|
||
Depends on D157823
Pushed by jvarga@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0e5d5b851391
Fix FileSystemWritableFileStream to use the default writer for all IO operations; r=dom-storage-reviewers,webidl,smaug,jari
Comment 3•3 years ago
|
||
Backed out for Hazard bustages on FileSystemWritableFileStream.cpp
Backout link: https://hg.mozilla.org/integration/autoland/rev/75e27831b02fc8f0cf306fd61717df9d534455d1
Log link: https://treeherder.mozilla.org/logviewer?job_id=399461644&repo=autoland&lineNumber=84656
Flags: needinfo?(jvarga)
Pushed by jvarga@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/aec85fd6e08a
Fix FileSystemWritableFileStream to use the default writer for all IO operations; r=dom-storage-reviewers,webidl,smaug,jari
Comment 5•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox110:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•