Closed Bug 1513021 Opened 3 years ago Closed 3 years ago
Enable the storage access API on desktop
47 bytes, text/x-phabricator-request
|Details | Review|
(An intent to ship email needs to be sent for this. We intend to enable this to ride the trains for 65.)
Attachment #9032298 - Attachment description: Bug 1513021 - Ship the Storage Access API on all desktop platform; → Bug 1513021 - Ship the Storage Access API on all desktop platforms;
Comment on attachment 9032298 [details] Bug 1513021 - Ship the Storage Access API on all desktop platforms; [Beta/Release Uplift Approval Request] Feature/Bug causing the regression: Not a regression User impact if declined: We'd like to ship this API in 65, please see the intent to ship thread for rationale: https://groups.google.com/forum/#!topic/mozilla.dev.platform/BZ36ZDV0Fik Is this code covered by automated tests?: Yes Has the fix been verified in Nightly?: Yes Needs manual test from QE?: No If yes, steps to reproduce: List of other uplifts needed: None Risk to taking this patch: Low Why is the change risky/not risky? (and alternatives if risky): This has been turned on in Nightly for a few cycles. The API itself will not do anything unless the default cookie restrictions feature (bug 1473978) is shipped, and it isn't yet known to be used by a lot of third-party trackers, so we expect the risk of shipping this API at this point to be minimal. String changes made/needed: None
Attachment #9032298 - Flags: approval-mozilla-beta?
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/2dc724f82cb1 Ship the Storage Access API on all desktop platforms; r=baku
Comment on attachment 9032298 [details] Bug 1513021 - Ship the Storage Access API on all desktop platforms; [Triage Comment] Already enabled on Nightly for a few cycles and doesn't do much by itself unless the default cookie restrictions are also enabled (which is not yet the case). Approved for 65.0b7 so as to not block any future decisions around this feature as we move forward.
Attachment #9032298 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Is there anything QA can/should be doing with this for now to be on the lookout for any regressions or functional issues?
(In reply to Ryan VanderMeulen [:RyanVM] from comment #6) > Is there anything QA can/should be doing with this for now to be on the > lookout for any regressions or functional issues? No specific QA needed here, this feature has been receiving QA on the Nightly train. (And yes, we should of course be watching for regressions.)
You need to log in before you can comment on or make changes to this bug.