Issue metadata
Sign in to add a comment
|
Extension API Modification: Add getReferrerChain function to chrome.safeBrowsingPrivate |
||||||||||||||||||||||||||
Issue descriptionExtension API Modification Proposal API Namespace: chrome.safeBrowsingPrivate API Owners: enamelites@google.com API Overview Doc: https://docs.google.com/document/d/1dwk1jArSwT8Nol9RpeKSO9NpqbFriFaTsMkd-Z1F4rg/edit?usp=sharing Design Doc: N/A Supplementary Resources: For internal use (Google only: see https://docs.google.com/document/d/1HC7MnNG9TGUHoe3HWS0Qdl40Yg6mAHAjqSyxtxxq1Sg/edit?usp=sharing)
,
Dec 21
,
Dec 21
Marking as SafeBrowsing-Triaged, since this requires no action from our end.
,
Dec 21
Untriaged w/o owners -> Assigned
,
Dec 28
Seems reasonable to me - it's a pretty well-scoped addition to an existing private API. +meacer@ for security.
,
Jan 2
Looks like the API is exposing existing information, lgtm too. |
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by vakh@chromium.org
, Dec 19