|
|
Created:
3 years, 8 months ago by Marti Wong Modified:
3 years, 7 months ago CC:
chromium-reviews, agrieve+watch_chromium.org, dfalcantara+watch_chromium.org, Leo Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionAllow to use measured width in translate overflow menu
When showing the overflow menu, we should use measured width (by
setting fixedWidth to false) to make sure all items fit inside the
menu.
When showing the language menu (with 100+ languages), we should use the
hardcoded width (fixedWidth = true) so that it won't take a long time
to measure all item widths.
BUG=709964
Review-Url: https://codereview.chromium.org/2824083003
Cr-Commit-Position: refs/heads/master@{#468518}
Committed: https://chromium.googlesource.com/chromium/src/+/9146de1595631f543f2388239efba1ed1362704a
Patch Set 1 #
Total comments: 7
Patch Set 2 : Sync + fix, add checkbox, set offset #
Total comments: 2
Patch Set 3 : fix some careless mistakes #Patch Set 4 : added TODO comment for menu bg #
Total comments: 6
Patch Set 5 : fix #
Total comments: 6
Patch Set 6 : fix #Patch Set 7 : remove unused function #Patch Set 8 : sync #
Messages
Total messages: 63 (32 generated)
The CQ bit was checked by martiw@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...
Description was changed from ========== Allow to use measured width in translate overflow menu When showing the overflow menu, we should use measured width to make sure all items fit inside the menu. When showing the language menu (with 100+ languages), we should use the hardcoded width so that it won't take a long time to measure all item widths. We should use separate TranslateMenuHelper instance for overflow menu and language menu so that each of them has it's own listPopupWindow. Otherwise, if they share the same listPopupWindow, there will be a jumpy animation and other ui bug when transforming from overflow menu to language menu. BUG=709964 ========== to ========== Allow to use measured width in translate overflow menu When showing the overflow menu, we should use measured width (by setting fixedWidth to false) to make sure all items fit inside the menu. When showing the language menu (with 100+ languages), we should use the hardcoded width (fixedWidth = true) so that it won't take a long time to measure all item widths. We should use separate TranslateMenuHelper instance for overflow menu and language menu so that each of them has it's own listPopupWindow. Otherwise, if they share the same listPopupWindow, there will be a jumpy animation and other ui bug when transforming from overflow menu to language menu. BUG=709964 ==========
martiw@chromium.org changed reviewers: + dfalcantara@chromium.org
Description was changed from ========== Allow to use measured width in translate overflow menu When showing the overflow menu, we should use measured width (by setting fixedWidth to false) to make sure all items fit inside the menu. When showing the language menu (with 100+ languages), we should use the hardcoded width (fixedWidth = true) so that it won't take a long time to measure all item widths. We should use separate TranslateMenuHelper instance for overflow menu and language menu so that each of them has it's own listPopupWindow. Otherwise, if they share the same listPopupWindow, there will be a jumpy animation and other ui bug when transforming from overflow menu to language menu. BUG=709964 ========== to ========== Allow to use measured width in translate overflow menu When showing the overflow menu, we should use measured width (by setting fixedWidth to false) to make sure all items fit inside the menu. When showing the language menu (with 100+ languages), we should use the hardcoded width (fixedWidth = true) so that it won't take a long time to measure all item widths. BUG=709964 ==========
PTAL thanks again~!! https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:84: void onTranslateMenuItemClicked(String code, int type); In the previous CL, I thought that overflow menu and 'more languages' menu could share the same TranslateMenuHelper object and when transforming from overflow item to 'more languages' menu, we don't need to dismiss the menu but we replace the items inside. This approach has 2 problems when width is changed: 1. jumpy animation 2. a ui bug (width suddenly change when clicking) Therefore, I suggest that we should use separate TranslateMenuHelper object for these 2 menus so that each of them has it's own listPopupWindow. We just dismiss the first one and showing another one. Since menu will always dismiss, the return boolean here is no longer needed.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:136: private int measureMenuWidth(TranslateMenuAdapter adapter) { This ends up creating the View for every single item in the list. Can you just do something like what InfoBarControlLayout#computeMinWidthRequiredForValues() does?
https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:127: mPopup.setWidth(measureMenuWidth(mAdapter) + bgPadding.left + bgPadding.right); test what happens if you set the width really large (larger than the phone screen is) https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:136: private int measureMenuWidth(TranslateMenuAdapter adapter) { On 2017/04/18 23:49:18, ping past 24hrs (dfalcantara) wrote: > This ends up creating the View for every single item in the list. Can you just > do something like what InfoBarControlLayout#computeMinWidthRequiredForValues() > does? If you fix your getView call to properly use the convertView, you're probably fine.
On 2017/04/19 01:50:50, ping past 24hrs (dfalcantara) wrote: > https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... > File > chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java > (right): > > https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... > chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:127: > mPopup.setWidth(measureMenuWidth(mAdapter) + bgPadding.left + bgPadding.right); > test what happens if you set the width really large (larger than the phone > screen is) > > https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... > chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:136: > private int measureMenuWidth(TranslateMenuAdapter adapter) { > On 2017/04/18 23:49:18, ping past 24hrs (dfalcantara) wrote: > > This ends up creating the View for every single item in the list. Can you > just > > do something like what InfoBarControlLayout#computeMinWidthRequiredForValues() > > does? > > If you fix your getView call to properly use the convertView, you're probably > fine. Thanks for the review~! Leo is working on the getView and make it uses the convertView properly. I will revisit this CL after his CL is landed. Thanks again!
Patchset #2 (id:20001) has been deleted
On 2017/04/19 04:00:09, Marti Wong wrote: > On 2017/04/19 01:50:50, ping past 24hrs (dfalcantara) wrote: > > > https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... > > File > > > chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java > > (right): > > > > > https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... > > > chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:127: > > mPopup.setWidth(measureMenuWidth(mAdapter) + bgPadding.left + > bgPadding.right); > > test what happens if you set the width really large (larger than the phone > > screen is) > > > > > https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... > > > chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:136: > > private int measureMenuWidth(TranslateMenuAdapter adapter) { > > On 2017/04/18 23:49:18, ping past 24hrs (dfalcantara) wrote: > > > This ends up creating the View for every single item in the list. Can you > > just > > > do something like what > InfoBarControlLayout#computeMinWidthRequiredForValues() > > > does? > > > > If you fix your getView call to properly use the convertView, you're probably > > fine. > > Thanks for the review~! > Leo is working on the getView and make it uses the convertView properly. > I will revisit this CL after his CL is landed. Thanks again! PTAL CL updated. It sets the menu y-offset (to shift down the menu to make it cover the menu button) And the checkbox layouts are added. thanks again~!
https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:127: mPopup.setWidth(measureMenuWidth(mAdapter) + bgPadding.left + bgPadding.right); On 2017/04/19 01:50:50, slow (dfalcantara) wrote: > test what happens if you set the width really large (larger than the phone > screen is) Tested. Menu width will be limited by the screen width. https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:136: private int measureMenuWidth(TranslateMenuAdapter adapter) { On 2017/04/18 23:49:18, slow (dfalcantara) wrote: > This ends up creating the View for every single item in the list. Can you just > do something like what InfoBarControlLayout#computeMinWidthRequiredForValues() > does? googleo@ has fixed getView and it won't create Views every time. see if it is okay now. https://codereview.chromium.org/2824083003/diff/1/chrome/android/java/src/org... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:136: private int measureMenuWidth(TranslateMenuAdapter adapter) { On 2017/04/19 01:50:50, slow (dfalcantara) wrote: > On 2017/04/18 23:49:18, ping past 24hrs (dfalcantara) wrote: > > This ends up creating the View for every single item in the list. Can you > just > > do something like what InfoBarControlLayout#computeMinWidthRequiredForValues() > > does? > > If you fix your getView call to properly use the convertView, you're probably > fine. Ack. Thanks.
PTAL CL updated. It sets the menu y-offset (to shift down the menu to make it cover the menu button) And the checkbox layouts are added. thanks again~!
dfalcantara@chromium.org changed reviewers: + twellington@chromium.org
Delegating to Theresa for menu placement.
https://codereview.chromium.org/2824083003/diff/40001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/40001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:109: } This menu placement lgtm (it's the same as what we're doing for the app menu in Chrome Home). The background we use for popup windows has shadows that make the placement not quite right when displayed at the bottom the screen, so I expect there will be some follow up polish needed. Are there screenshots of what this currently looks like?
The CQ bit was checked by martiw@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...
Thanks Dan and Theresa. Below is the screenshot: https://drive.google.com/open?id=0B1O0Z7eoZMuGZXhOU0VsM2RKMGM https://codereview.chromium.org/2824083003/diff/40001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/40001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:109: } On 2017/04/26 18:10:17, Theresa wrote: > This menu placement lgtm (it's the same as what we're doing for the app menu in > Chrome Home). > > The background we use for popup windows has shadows that make the placement not > quite right when displayed at the bottom the screen, so I expect there will be > some follow up polish needed. Are there screenshots of what this currently looks > like? Thanks for the advice. Yah it seems we might need a background with less drop shadow at the bottom. I added a TODO here.
On 2017/04/27 00:37:29, Marti Wong wrote: > Thanks Dan and Theresa. > > Below is the screenshot: > https://drive.google.com/open?id=0B1O0Z7eoZMuGZXhOU0VsM2RKMGM > > https://codereview.chromium.org/2824083003/diff/40001/chrome/android/java/src... > File > chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java > (right): > > https://codereview.chromium.org/2824083003/diff/40001/chrome/android/java/src... > chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:109: > } > On 2017/04/26 18:10:17, Theresa wrote: > > This menu placement lgtm (it's the same as what we're doing for the app menu > in > > Chrome Home). > > > > The background we use for popup windows has shadows that make the placement > not > > quite right when displayed at the bottom the screen, so I expect there will be > > some follow up polish needed. Are there screenshots of what this currently > looks > > like? > > Thanks for the advice. Yah it seems we might need a background with less drop > shadow at the bottom. I added a TODO here. Hi Dan & Theresa, See if you'll have other comments besides menu placement. Thanks again~!
googleo@chromium.org changed reviewers: + googleo@chromium.org
Add some comments. https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java (right): https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java:83: if (mLanguageMenuHelper == null) { Maybe you can pass the menu type to init the type of menu helper when it's needed. https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenu.java (right): https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenu.java:66: OVERFLOW_MENU.add(new MenuItem( We shouldn't toggle the logic here. This is a static method used for all Tabs. I think we should always return Checkbox item type, then set the checkbox status selected or not when rendering the menu item. https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:40: private final int[] mTempLocation; This is only used between the line 132~135, right? Why not create it on demand.
The CQ bit was checked by martiw@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 martiw@chromium.org
Fixed things according to Leo's comments. PTAL and see if there's any thing else. thx~! https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java (right): https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java:83: if (mLanguageMenuHelper == null) { On 2017/04/27 06:25:48, Leo wrote: > Maybe you can pass the menu type to init the type of menu helper when it's > needed. Done. thanks~! https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenu.java (right): https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenu.java:66: OVERFLOW_MENU.add(new MenuItem( On 2017/04/27 06:25:48, Leo wrote: > We shouldn't toggle the logic here. This is a static method used for all Tabs. > > I think we should always return Checkbox item type, then set the checkbox status > selected or not when rendering the menu item. Done. https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/80001/chrome/android/java/src... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:40: private final int[] mTempLocation; On 2017/04/27 06:25:48, Leo wrote: > This is only used between the line 132~135, right? > Why not create it on demand. Done.
lgtm % comments https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... File chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java (right): https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java:33: // Need 2 instances of TranslateMenuHelper to prevent a racing condition bug which happens when race condition. https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:102: if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) { Should this be moved to ApiCompatibilityUtils#setVerticalOffset(ListPopupWindow, baseOffset, anchorHeight)? https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:118: // Use measured width when it is a overflow menu periods everywhere
Thanks guys for the review. Committing https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... File chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java (right): https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java:33: // Need 2 instances of TranslateMenuHelper to prevent a racing condition bug which happens when On 2017/04/27 18:56:18, slow (dfalcantara) wrote: > race condition. Done. https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... File chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java (right): https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:102: if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) { On 2017/04/27 18:56:18, slow (dfalcantara) wrote: > Should this be moved to ApiCompatibilityUtils#setVerticalOffset(ListPopupWindow, > baseOffset, anchorHeight)? Thanks for the advice! I will leave this alone at the moment. If we made ApiCompatibilityUtils#setVerticalOffset, AppMenu.java and this file could be the only places to use that. But I still could not fully understand AppMenu.java (why padding.bottom and mNegativeSoftwareVerticalOffset don't need to change sign). not confident to touch that. https://codereview.chromium.org/2824083003/diff/100001/chrome/android/java/sr... chrome/android/java/src/org/chromium/chrome/browser/infobar/translate/TranslateMenuHelper.java:118: // Use measured width when it is a overflow menu On 2017/04/27 18:56:18, slow (dfalcantara) wrote: > periods everywhere Done.
The CQ bit was checked by martiw@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from twellington@chromium.org, dfalcantara@chromium.org Link to the patchset: https://codereview.chromium.org/2824083003/#ps140001 (title: "remove unused function")
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: cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...) chromeos_amd64-generic_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-...) chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
The CQ bit was checked by martiw@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: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
The CQ bit was checked by martiw@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: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by martiw@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: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...) linux_chromium_compile_dbg_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 martiw@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: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...) android_compile_dbg on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...) android_cronet on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_cron...) linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...) linux_chromium_chromeos_ozone_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 martiw@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: android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...) android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...) cast_shell_android on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...) chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...) linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
This is going to keep failing until you sync.
Thanks Dan! Will do the sync when I back to office tmr. On Sun, 30 Apr 2017 at 11:27 AM <dfalcantara@chromium.org> wrote: > This is going to keep failing until you sync. > > https://codereview.chromium.org/2824083003/ > -- You received this message because you are subscribed to the Google Groups "Chromium-reviews" group. To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
The CQ bit was checked by martiw@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from twellington@chromium.org, dfalcantara@chromium.org Link to the patchset: https://codereview.chromium.org/2824083003/#ps160001 (title: "sync")
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 160001, "attempt_start_ts": 1493683889992270, "parent_rev": "dda54d9447069a3c5dd62fc547ae71f6ff28766e", "commit_rev": "9146de1595631f543f2388239efba1ed1362704a"}
Message was sent while issue was closed.
Description was changed from ========== Allow to use measured width in translate overflow menu When showing the overflow menu, we should use measured width (by setting fixedWidth to false) to make sure all items fit inside the menu. When showing the language menu (with 100+ languages), we should use the hardcoded width (fixedWidth = true) so that it won't take a long time to measure all item widths. BUG=709964 ========== to ========== Allow to use measured width in translate overflow menu When showing the overflow menu, we should use measured width (by setting fixedWidth to false) to make sure all items fit inside the menu. When showing the language menu (with 100+ languages), we should use the hardcoded width (fixedWidth = true) so that it won't take a long time to measure all item widths. BUG=709964 Review-Url: https://codereview.chromium.org/2824083003 Cr-Commit-Position: refs/heads/master@{#468518} Committed: https://chromium.googlesource.com/chromium/src/+/9146de1595631f543f2388239efb... ==========
Message was sent while issue was closed.
Committed patchset #8 (id:160001) as https://chromium.googlesource.com/chromium/src/+/9146de1595631f543f2388239efb... |