On 10/30/24 7:54 PM, Chromestatus wrote:
Contact emails
est...@chromium.org
Specification
https://storage.spec.whatwg.org
Summary
navigator.storage is no longer an EventTarget navigator.storage was
made an EventTarget for the Storage Pressure Event, which never made
it past the prototype phase:
https://chromestatus.com/feature/5666274359115776 This dead code is
being removed and as a result, navigator.storage will no longer extend
EventTarget.
Blink component
Blink>Storage>Quota
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink>Storage>Quota>
TAG review
None
TAG review status
Not applicable
Risks
Interoperability and Compatibility
This change is technically web-facing, but it brings Chromium in line
with other browser vendors. It's very unlikely any site used the
functionality because Chromium never fired an event at
navigator.storage except in developer builds.
Bringing us in line with other browsers is good, but not necessarily a
guarantee that things won't go wrong. Have we done any kind of research
to determine that sites weren't attempting to use this?
At the very least, having the ability to kill-switch this with a flag
would be advisable - right now this PSA suggests otherwise.
/Gecko/: No signal
/WebKit/: No signal
/Web developers/: No signals
/Other signals/:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such
that it has potentially high risk for Android WebView-based applications?
None
Debuggability
None
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
Yes
Flag name on chrome://flags
None
Finch feature name
None
Non-finch justification
None
Requires code in //chrome?
False
Estimated milestones
Shipping on desktop 132
Shipping on Android 132
Anticipated spec changes
Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github
issues in the project for the feature specification) whose resolution
may introduce web compat/interop risk (e.g., changing to naming or
structure of the API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5132158480678912?gate=5665876618248192
This intent message was generated by Chrome Platform Status
<https://chromestatus.com>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6722c71d.2b0a0220.230002.023f.GAE%40google.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6722c71d.2b0a0220.230002.023f.GAE%40google.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e53e854a-7b24-4db8-9639-bc351ad7cbbe%40chromium.org.
