|
|
DescriptionEnable the MD User Menu by default on trunk.
BUG=616242
Committed: https://crrev.com/e3c600aa49b1e2bed95bfe9298a733bd72a0cb4e
Cr-Commit-Position: refs/heads/master@{#423787}
Patch Set 1 #Patch Set 2 : Fix Unit Tests. #
Total comments: 4
Patch Set 3 : Address feedback on cocoa tests. #
Total comments: 2
Messages
Total messages: 44 (30 generated)
anthonyvd@chromium.org changed reviewers: + rogerta@chromium.org
Hi Roger, this change enables the new User Menu by default on ToT. Can you PTAL? Thanks!
lgtm
The CQ bit was checked by anthonyvd@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by anthonyvd@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by anthonyvd@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by anthonyvd@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by anthonyvd@chromium.org
The CQ bit was checked by anthonyvd@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by anthonyvd@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by anthonyvd@chromium.org
The CQ bit was checked by anthonyvd@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Patchset #6 (id:100001) has been deleted
Patchset #5 (id:80001) has been deleted
Patchset #4 (id:60001) has been deleted
Patchset #3 (id:40001) has been deleted
Patchset #2 (id:20001) has been deleted
anthonyvd@chromium.org changed reviewers: + maxbogue@chromium.org, rsesek@chromium.org, sky@chromium.org
Hi everyone, We're enabling the Material Design User Menu on ToT and the flag being enabled by default broke some tests. This CL enables the flag by default and fixes those tests. Can you PTAL? maxbogue@: c/b/sync/ sky@: c/b/ui/views/profiles/ rsesek@: c/b/ui/cocoa/profiles/ Thanks a lot!
https://codereview.chromium.org/2396893002/diff/120001/chrome/browser/ui/coco... File chrome/browser/ui/cocoa/profiles/profile_chooser_controller_unittest.mm (right): https://codereview.chromium.org/2396893002/diff/120001/chrome/browser/ui/coco... chrome/browser/ui/cocoa/profiles/profile_chooser_controller_unittest.mm:218: NSUInteger last_subview_index = switches::IsMaterialDesignUserMenu() ? 4 : 2; These tests are incorrectly using camelCase for variable names (when under_score is appropriate for C++ functions). But consistency is the overriding style rule, so this should probably be named lastSubviewIndex (and throughout the CL). https://codereview.chromium.org/2396893002/diff/120001/chrome/browser/ui/coco... chrome/browser/ui/cocoa/profiles/profile_chooser_controller_unittest.mm:298: auto views_count = switches::IsMaterialDesignUserMenu() ? 5U : 3U; Use NSUInteger instead of auto and drop the 'U's?
https://codereview.chromium.org/2396893002/diff/120001/chrome/browser/ui/coco... File chrome/browser/ui/cocoa/profiles/profile_chooser_controller_unittest.mm (right): https://codereview.chromium.org/2396893002/diff/120001/chrome/browser/ui/coco... chrome/browser/ui/cocoa/profiles/profile_chooser_controller_unittest.mm:218: NSUInteger last_subview_index = switches::IsMaterialDesignUserMenu() ? 4 : 2; On 2016/10/06 at 18:49:35, Robert Sesek wrote: > These tests are incorrectly using camelCase for variable names (when under_score is appropriate for C++ functions). But consistency is the overriding style rule, so this should probably be named lastSubviewIndex (and throughout the CL). Ahh, makes sense! Done everywhere. https://codereview.chromium.org/2396893002/diff/120001/chrome/browser/ui/coco... chrome/browser/ui/cocoa/profiles/profile_chooser_controller_unittest.mm:298: auto views_count = switches::IsMaterialDesignUserMenu() ? 5U : 3U; On 2016/10/06 at 18:49:35, Robert Sesek wrote: > Use NSUInteger instead of auto and drop the 'U's? Done.
lgtm w/ question https://codereview.chromium.org/2396893002/diff/140001/chrome/browser/sync/sy... File chrome/browser/sync/sync_global_error_unittest.cc (right): https://codereview.chromium.org/2396893002/diff/140001/chrome/browser/sync/sy... chrome/browser/sync/sync_global_error_unittest.cc:129: if (switches::IsMaterialDesignUserMenu()) Presumably at some point this switch will be removed and then this entire test would be removed as well?
https://codereview.chromium.org/2396893002/diff/140001/chrome/browser/sync/sy... File chrome/browser/sync/sync_global_error_unittest.cc (right): https://codereview.chromium.org/2396893002/diff/140001/chrome/browser/sync/sy... chrome/browser/sync/sync_global_error_unittest.cc:129: if (switches::IsMaterialDesignUserMenu()) On 2016/10/06 at 19:22:36, maxbogue wrote: > Presumably at some point this switch will be removed and then this entire test would be removed as well? Absolutely. There's going to be some clean up involved when removing that switch and this is part of it.
LGTM
LGTM
The CQ bit was checked by anthonyvd@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from rogerta@chromium.org Link to the patchset: https://codereview.chromium.org/2396893002/#ps140001 (title: "Address feedback on cocoa tests.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #3 (id:140001)
Message was sent while issue was closed.
Description was changed from ========== Enable the MD User Menu by default on trunk. BUG=616242 ========== to ========== Enable the MD User Menu by default on trunk. BUG=616242 Committed: https://crrev.com/e3c600aa49b1e2bed95bfe9298a733bd72a0cb4e Cr-Commit-Position: refs/heads/master@{#423787} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/e3c600aa49b1e2bed95bfe9298a733bd72a0cb4e Cr-Commit-Position: refs/heads/master@{#423787} |