|
|
Chromium Code Reviews|
Created:
7 years, 6 months ago by noms (inactive) Modified:
7 years, 6 months ago Reviewers:
Roger Tawa OOO till Jul 10th, Pam (message me for reviews), Andrew T Wilson (Slow), nasko CC:
tim (not reviewing), Roger Tawa OOO till Jul 10th, bcwhite, fdoray, Andrew T Wilson (Slow), jln (very slow on Chromium), nasko Base URL:
https://chromium.googlesource.com/chromium/src.git@master Visibility:
Public. |
DescriptionDisplay confirmation dialog for untrusted signins
BUG=252062
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=208520
Patch Set 1 #
Total comments: 5
Patch Set 2 : review comments #Patch Set 3 : fix whitespace #
Total comments: 2
Patch Set 4 : added EnsureBrowser() #Patch Set 5 : rebased #
Total comments: 1
Messages
Total messages: 25 (0 generated)
https://codereview.chromium.org/17482002/diff/1/chrome/browser/ui/sync/one_cl... File chrome/browser/ui/sync/one_click_signin_helper.cc (right): https://codereview.chromium.org/17482002/diff/1/chrome/browser/ui/sync/one_cl... chrome/browser/ui/sync/one_click_signin_helper.cc:233: args.confirmation_required; Can probably get rid of this local var too. Its now only used once at line 239. https://codereview.chromium.org/17482002/diff/1/chrome/browser/ui/sync/one_cl... chrome/browser/ui/sync/one_click_signin_helper.cc:991: untrusted_confirmation_required_ = true; I don't think this change and the one at line 1063 below are strictly required, since the untrusted check is performed at the end of GAIA sign in process when we get the G-A-S header. However, these changes are useful in case the process swap logic fails for some reason. https://codereview.chromium.org/17482002/diff/1/chrome/browser/ui/sync/one_cl... chrome/browser/ui/sync/one_click_signin_helper.cc:1154: false /* confirmation_required */, source_), I think we should change this false to a true as well. Its not explicitly mentioned in the bug, but we are disabling confirmation here because we assume the advanced sync config dialog will handle aborting the sign in, but it no longer does.
https://codereview.chromium.org/17482002/diff/1/chrome/browser/ui/sync/one_cl... File chrome/browser/ui/sync/one_click_signin_helper.cc (right): https://codereview.chromium.org/17482002/diff/1/chrome/browser/ui/sync/one_cl... chrome/browser/ui/sync/one_click_signin_helper.cc:233: args.confirmation_required; On 2013/06/20 07:51:29, Roger Tawa wrote: > Can probably get rid of this local var too. Its now only used once at line 239. Done. https://codereview.chromium.org/17482002/diff/1/chrome/browser/ui/sync/one_cl... chrome/browser/ui/sync/one_click_signin_helper.cc:991: untrusted_confirmation_required_ = true; As discussed, removed this change. On 2013/06/20 07:51:29, Roger Tawa wrote: > I don't think this change and the one at line 1063 below are strictly required, > since the untrusted check is performed at the end of GAIA sign in process when > we get the G-A-S header. However, these changes are useful in case the process > swap logic fails for some reason.
lgtm Thanks Monica! https://codereview.chromium.org/17482002/diff/7001/chrome/browser/ui/sync/one... File chrome/browser/ui/sync/one_click_signin_sync_starter.cc (right): https://codereview.chromium.org/17482002/diff/7001/chrome/browser/ui/sync/one... chrome/browser/ui/sync/one_click_signin_sync_starter.cc:320: chrome::NavigateParams params(browser_, GURL(chrome::kChromeUINewTabURL), I wonder if you should call EnsureBrowser() here, like is done at line 387 below. This could happen if the user closes the browser window before the starter is done.
https://codereview.chromium.org/17482002/diff/7001/chrome/browser/ui/sync/one... File chrome/browser/ui/sync/one_click_signin_sync_starter.cc (right): https://codereview.chromium.org/17482002/diff/7001/chrome/browser/ui/sync/one... chrome/browser/ui/sync/one_click_signin_sync_starter.cc:320: chrome::NavigateParams params(browser_, GURL(chrome::kChromeUINewTabURL), On 2013/06/21 17:06:22, Roger Tawa wrote: > I wonder if you should call EnsureBrowser() here, like is done at line 387 > below. This could happen if the user closes the browser window before the > starter is done. Done.
+ pam for owners stamp on chrome/browser/ui/webui/inline_login_ui.cc
LGTM. Just a note, this kind of change -- only adjusting a method call to match a change already approved in another part of the code -- can be also done with TBR owner approval. - Pam
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
Retried try job too often on chromium_presubmit for step(s) presubmit http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
Drive by: Why is this change missing a test? How will we detect regression to this if we don't have one?
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
Retried try job too often on chromium_presubmit for step(s) presubmit http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
Retried try job too often on chromium_presubmit for step(s) presubmit http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...
https://codereview.chromium.org/17482002/diff/18001/chrome/browser/ui/sync/on... File chrome/browser/ui/sync/one_click_signin_helper.cc (right): https://codereview.chromium.org/17482002/diff/18001/chrome/browser/ui/sync/on... chrome/browser/ui/sync/one_click_signin_helper.cc:1150: true /* confirmation_required */, source_), Why are we *always* displaying this confirmation, and not just only in the case where untrusted_confirmation_required == true? Doesn't this display an extra confirmation even in a trusted GAIA flow?
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
Retried try job too often on chromium_presubmit for step(s) presubmit http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
Retried try job too often on chromium_presubmit for step(s) presubmit http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/noms@chromium.org/17482002/18001
Message was sent while issue was closed.
Change committed as 208520 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
