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

Issue 1989543002: MacViews: support Views device permission prompt (Closed)

Created:
4 years, 7 months ago by Elly Fong-Jones
Modified:
4 years, 7 months ago
Reviewers:
tapted, sky
CC:
chromium-reviews, chromium-apps-reviews_chromium.org, tfarina, extensions-reviews_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

MacViews: support Views device permission prompt This is a straightforward conversion. The Views implementation is moved ontoo Mac, and a shim added for the Cocoa implementation to optionally summon the Views version of the dialog. Screenshots of both dialogs are attached to the bug. BUG=610430 Committed: https://crrev.com/b74909cbced955d38dd10db3dbb0252d32a5f91b Cr-Commit-Position: refs/heads/master@{#394252}

Patch Set 1 #

Patch Set 2 : rebase #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+15 lines, -3 lines) Patch
M chrome/browser/extensions/api/chrome_device_permissions_prompt.h View 1 chunk +4 lines, -0 lines 0 comments Download
M chrome/browser/ui/cocoa/extensions/device_permissions_dialog_controller.mm View 2 chunks +3 lines, -0 lines 1 comment Download
M chrome/browser/ui/views/browser_dialogs_views.cc View 1 2 chunks +5 lines, -0 lines 0 comments Download
M chrome/browser/ui/views/extensions/device_permissions_dialog_view.cc View 1 chunk +1 line, -1 line 0 comments Download
M chrome/chrome_browser_ui.gypi View 1 2 chunks +2 lines, -2 lines 0 comments Download

Messages

Total messages: 16 (8 generated)
Elly Fong-Jones
tapted, sky: ptal? :)
4 years, 7 months ago (2016-05-17 16:59:10 UTC) #3
sky
LGTM
4 years, 7 months ago (2016-05-17 18:18:26 UTC) #4
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1989543002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1989543002/1
4 years, 7 months ago (2016-05-17 18:39:43 UTC) #6
commit-bot: I haz the power
Try jobs failed on following builders: mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_compile_dbg_ng/builds/204925) mac_chromium_gn_rel on tryserver.chromium.mac (JOB_FAILED, ...
4 years, 7 months ago (2016-05-17 18:42:51 UTC) #8
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1989543002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1989543002/20001
4 years, 7 months ago (2016-05-17 18:58:56 UTC) #11
commit-bot: I haz the power
Committed patchset #2 (id:20001)
4 years, 7 months ago (2016-05-17 22:43:16 UTC) #13
commit-bot: I haz the power
Patchset 2 (id:??) landed as https://crrev.com/b74909cbced955d38dd10db3dbb0252d32a5f91b Cr-Commit-Position: refs/heads/master@{#394252}
4 years, 7 months ago (2016-05-17 22:46:24 UTC) #15
tapted
4 years, 7 months ago (2016-05-18 00:14:52 UTC) #16
Message was sent while issue was closed.
lgtm - there's a comment but it's more a bit of trivia/curiosity (and it's in
device_permissions_dialog_controller.mm which is probably one of the first Cocoa
files we'll be able to purge).

https://codereview.chromium.org/1989543002/diff/20001/chrome/browser/ui/cocoa...
File chrome/browser/ui/cocoa/extensions/device_permissions_dialog_controller.mm
(right):

https://codereview.chromium.org/1989543002/diff/20001/chrome/browser/ui/cocoa...
chrome/browser/ui/cocoa/extensions/device_permissions_dialog_controller.mm:61:
return ChromeDevicePermissionsPrompt::ShowDialogViews();
I can't decide whether this is cool or sneaky :). C++ lets you return a "void"
value from a void function, but it usually just gets exploited in templated
code. Nothing really wrong with it I guess - just a bit obscure.  (also this
line could just be `return ShowDialogViews();` - the method isn't static - but
in some ways it's a nice indication that the call isn't to code that's "nearby",
so this is fine too).

Powered by Google App Engine
This is Rietveld 408576698