Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(231)

Issue 2804913005: Don't use the DSE geolocation setting when chrome doesn't have location. (Closed)

Created:
3 years, 8 months ago by benwells
Modified:
3 years, 8 months ago
Reviewers:
dominickn
CC:
chromium-reviews, chrome-apps-syd-reviews_chromium.org
Target Ref:
refs/heads/master
Project:
chromium
Visibility:
Public.

Description

Don't use the DSE geolocation setting when chrome doesn't have location. The DSE geolocation setting controls whether the default search engine should have geolocation access or not, and is on by default. When the setting is used and chrome does not have permission at the android level, Chrome will ask the user to give Chrome location access. What this all means is that if the DSE location setting is used on a device where Chrome doesn't have geolocation access, the user will be prompted to give Chrome location access on every google search (whether via the search results page or the omnibox). This change prevents this by preventing the DSE geolocation setting from being used if Chrome doesn't have geolocation access. BUG=709219 Review-Url: https://codereview.chromium.org/2804913005 Cr-Commit-Position: refs/heads/master@{#463057} Committed: https://chromium.googlesource.com/chromium/src/+/235d2d36366b8eefb2f167de9432f546a7752e47

Patch Set 1 #

Patch Set 2 : Fix tests #

Patch Set 3 : Fix other test #

Unified diffs Side-by-side diffs Delta from patch set Stats (+26 lines, -2 lines) Patch
M chrome/browser/android/search_geolocation/search_geolocation_service.h View 1 2 chunks +4 lines, -0 lines 0 comments Download
M chrome/browser/android/search_geolocation/search_geolocation_service.cc View 1 4 chunks +11 lines, -1 line 0 comments Download
M chrome/browser/android/search_geolocation/search_geolocation_service_unittest.cc View 1 3 chunks +9 lines, -1 line 0 comments Download
M chrome/browser/geolocation/geolocation_permission_context_unittest.cc View 1 2 1 chunk +2 lines, -0 lines 0 comments Download

Messages

Total messages: 22 (16 generated)
benwells
3 years, 8 months ago (2017-04-07 04:54:39 UTC) #4
dominickn
lgtm
3 years, 8 months ago (2017-04-07 05:12:23 UTC) #5
dominickn
still lgtm
3 years, 8 months ago (2017-04-07 22:58:00 UTC) #16
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2804913005/40001
3 years, 8 months ago (2017-04-07 23:22:35 UTC) #18
commit-bot: I haz the power
Committed patchset #3 (id:40001) as https://chromium.googlesource.com/chromium/src/+/235d2d36366b8eefb2f167de9432f546a7752e47
3 years, 8 months ago (2017-04-07 23:55:17 UTC) #21
benwells
3 years, 8 months ago (2017-04-12 01:08:13 UTC) #22
Message was sent while issue was closed.
A revert of this CL (patchset #3 id:40001) has been created in
https://codereview.chromium.org/2811073003/ by benwells@chromium.org.

The reason for reverting is: We are going with a server side fix instead for
this problem. We should still investigate separately some means of backing off
the Update Permissions prompt (e.g. with embargo)..

Powered by Google App Engine
This is Rietveld 408576698