New Extension API: chrome.safeBrowsingPrivate |
|||||||||||||||||
Issue descriptionNew Extension API Proposal API Namespace: chrome.safeBrowsingPrivate API Owners: chrome-safebrowsing@google.com API Overview Doc: https://docs.google.com/document/d/1A2hhK2tCTAkUYkiDngcifplvpI7r7f4x2OxgoynQFkg/edit?usp=sharing Design Doc: https://docs.google.com/document/d/1ehs1JXtA5zzIJ55p_wDN9bFtZeIzKm9kdth9gVELvTg/edit?ts=5a7b9e54#heading=h.xszfgvbu9hc0 Supplementary Resources:
,
Feb 9 2018
[Extensions Triage]: Marking as Assigned.
,
Feb 9 2018
,
Feb 12 2018
,
Feb 12 2018
,
Feb 21 2018
rdevlin.cronin@, I believe I've resolved all your comments on the design doc and the API overview doc. What's next? Any label I should flip to trigger privacy/security reviews?
,
Feb 22 2018
Sorry for the delay; unburying myself from OOO. :) This looks fine from an API perspective; flipping the bit. meacer@, mind taking a look for security (or punting along appropriately?)
,
Feb 22 2018
Security lgtm too.
,
Feb 26 2018
Who should I ping for privacy review?
,
Mar 13 2018
msramek@ is a good starting point for privacy; Martin, can you take a look or forward appropriately?
,
Mar 13 2018
+Ramin, can you PTAL at this from privacy perspective?
,
Mar 20 2018
,
Mar 27 2018
Dear Chrome privacy team, Could you let me know if there's anything blocking the review? We've already missed M66, M67 feature freeze is coming this Friday. We'd appreciate if we can at least have a ETA of this review.
,
Mar 28 2018
Sorry, most of the team is out now, including Ramin. Let me ping this bug next week.
,
Apr 4 2018
The NextAction date has arrived: 2018-04-04
,
Apr 4 2018
,
Apr 6 2018
Flipping the privacy bit.
,
Apr 9 2018
Assigning back to jialiul@ as privacy review is LTGMed.
,
Apr 9 2018
Thanks rhalavati@! and thanks everyone!
,
Jun 1 2018
,
Aug 13
|
|||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||
Comment 1 by jialiul@chromium.org
, Feb 7 2018