Extension API Modification: Add service workers and cache storage to browsingData.remove api |
|||||||
Issue descriptionExtension API Modification Proposal API Namespace: browsingData API Owners: dullweber@, chrome-privacy-core@ API Overview Doc: https://docs.google.com/document/d/1dhF4FJ22bF8c6Gy4JyfB6Ke74hJOtityPr6CvK41daQ/edit?usp=sharing I don't know if there is an existing api doc for browsingData. Add browsingData.removeServiceWorkers and browsingData.removeCacheStorage functions.
,
Nov 7
Requesting reviews for this small proposal. I don't think ui-review is neccessary as this doesn't affect any ui.
,
Nov 9
Assigning to myself so I remember to take a look at this.
,
Nov 12
The NextAction date has arrived: 2018-11-12
,
Nov 12
No significant security risk in addition to what chrome.browsingData already has, lgtm.
,
Nov 14
LGTM2. chrome.browsingData already covers several web-facing storage mechanisms (e.g. cookies, local storage, indexed db). Not supporting all such storage mechanisms actually makes it ineffective at its task (as the extensions currently can't clear all of user's data and protect them from tracking), which means this addition is privacy-positive.
,
Nov 16
API LGTM. +crx security FYI.
,
Nov 19
Thanks everyone. I'm not sure about the launch process for extensions. This is just a small change to an existing API, so I guess a waterfall roll-out is fine and I can just close this bug? |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dullweber@chromium.org
, Nov 5