New issue
Advanced search Search tips

Issue 914411 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature
Launch-Privacy: NotReviewed
Launch-Security: Yes
Launch-UI: NotReviewed



Sign in to add a comment

Extension API Modification: Add getReferrerChain function to chrome.safeBrowsingPrivate

Project Member Reported by livvielin@chromium.org, Dec 12

Issue description

Extension 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)

 
Components: Services>Safebrowsing
Cc: rdevlin....@chromium.org
Owner: livvielin@chromium.org
Labels: SafeBrowsing-Triaged
Marking as SafeBrowsing-Triaged, since this requires no action from our end.
Status: Assigned (was: Untriaged)
Untriaged w/o owners -> Assigned
Cc: mea...@chromium.org
Labels: -Launch-API-NotReviewed Launch-API-Yes
Seems reasonable to me - it's a pretty well-scoped addition to an existing private API.  +meacer@ for security.
Labels: -Launch-Security-NotReviewed Launch-Security-Yes
Looks like the API is exposing existing information, lgtm too.

Sign in to add a comment