Issue metadata
Sign in to add a comment
|
Investigate how permissions embargo interacts with search geolocation disclosure / default search engine geolocation |
||||||||||||||||||||||||
Issue descriptionLet's say the user has a search engine with geolocation permission embargoed. What should happen when the user changes their default search engine to the embargoed engine? a) wipe embargo and restore state to ASK b) respect embargo and do not grant geolocation to the new default search engine emilyschechter: do you have thoughts on this from the PM perspective?
,
Jun 8 2017
I agree with that. Let's go with #1.
,
Jun 15 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/19a5b3587d246544ad1927e6c891e00df2061c49 commit 19a5b3587d246544ad1927e6c891e00df2061c49 Author: benwells <benwells@chromium.org> Date: Thu Jun 15 04:47:56 2017 Reset geolocation permission embargo for an origin when it becomes DSE If an origin becomes the default search engine (DSE) it should have any embargo status on it reset. BUG= 730377 Review-Url: https://codereview.chromium.org/2941753002 Cr-Commit-Position: refs/heads/master@{#479606} [modify] https://crrev.com/19a5b3587d246544ad1927e6c891e00df2061c49/chrome/browser/android/search_geolocation/search_geolocation_service.cc [modify] https://crrev.com/19a5b3587d246544ad1927e6c891e00df2061c49/chrome/browser/android/search_geolocation/search_geolocation_service_unittest.cc
,
Jun 15 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by emilyschechter@chromium.org
, Jun 7 2017