Enable OPFS by default on Nightly
Categories
(Core :: DOM: File, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox110 | --- | fixed |
People
(Reporter: jesup, Assigned: jesup)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Attachments
(1 file, 1 obsolete file)
This is the flip the pref to enable in nightly, targeted at early 106
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Don't we need to add various interfaces to
https://searchfox.org/mozilla-central/source/dom/tests/mochitest/general/test_interfaces.js
and
https://searchfox.org/mozilla-central/source/dom/workers/test/test_worker_interfaces.js
Comment 3•2 years ago
|
||
And change the annotations in https://searchfox.org/mozilla-central/source/testing/web-platform/meta/fs/idlharness.https.any.js.ini? And presumably we've gone through the other annotations in https://searchfox.org/mozilla-central/source/testing/web-platform/meta/fs to make sure that we're not failing on anything fundamental or unexpected?
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 4•2 years ago
|
||
Intent to prototype and ship sent to dev-platform on xx-xx-xx
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Comment 6•2 years ago
|
||
Comment 7•2 years ago
|
||
Comment 8•2 years ago
|
||
Comment 10•2 years ago
|
||
Backed out changeset bc0b215802bb (Bug 1785123) for causing mochitest failures on test_privateWin.html.
Backout link
Push with failures <--> c3
Failure Log
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
Comment 13•2 years ago
|
||
bugherder |
Comment 14•2 years ago
|
||
MDN work can be tracked here https://github.com/mdn/content/issues/23688
Comment 15•2 years ago
•
|
||
Docs work is mostly an update to experimental features page and browser compatibility update.
Should we (is it useful to) record the quotas available to each browser/origin? We could do this by adding a note to the browser compat data if you think it would be helpful. I tried out navigator.storage.estimate()
and that indicates FF allocates about 10.7GB. I know that the amount returned is designed to prevent fingerprinting, but I was thinking that knowing the ballbark figure would tell users with a lot of data whether it is worth attempting to use this storage.
EDIT Note that I will mark dev-doc-complete, but can wake this up again if you decide that indicating the approximate amount available to each origin is a useful thing to do for different browsers.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Description
•