New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 730378 link

Starred by 1 user
Status: WontFix
Owner:
timloh@chromium.org
Closed: Aug 2017
Cc:
█ raymes@chromium.org
benwells@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Team-Security-UX



Sign in to add a comment

Android geolocation header should query permissions layer, not content settings

Project Member Reported by dominickn@chromium.org, Jun 7 2017 
We need to ensure that GeolocationHeader.java correctly respects permissions embargo by verifying that it checks permissions against the PermissionManager, not directly with content settings.

Comment 1 by benwells@chromium.org, Jun 7 2017

Labels: M-61

Comment 2 by benwells@chromium.org, Aug 1 2017

Cc: benwells@chromium.org
Labels: -M-61
Owner: timloh@chromium.org
Oh, another one (sorry!)

Comment 3 by timloh@chromium.org, Aug 2 2017 

Looks OK to me. GeolocationHeader uses GeolocationInfo.getContentSetting which calls GetGeolocationSettingForOrigin, and that queries the PermissionManager.

Comment 4 by benwells@chromium.org, Aug 2 2017

Status: WontFix (was: Assigned)
Goodo then :)
►

Sign in to add a comment