Fixed
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Expected output
What is the expected output?
Current output
What is the current output?
logcat output
Seehttp://developer.android.com/tools/help/logcat.html . Copy and paste relevant sections of the logcat output into this issue.
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Expected output
What is the expected output?
Current output
What is the current output?
logcat output
See
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
vi...@google.com <vi...@google.com> #3
Please provide the information as requested in comment #2 , For us to further investigate this issue.
li...@gmail.com <li...@gmail.com> #4
I am very sorry to reply this so late. i thought it was very clear in comment #1 .
This is not a bug, just want to add a new feature.
In my case, i need to expand the height of the toolbar, and we want the menu button to be vertically in center of this toolbar, but buttonGravity api only accept Gravity.TOP or Gravity.BOTTOM, so we can only achieve it in a hack way ( set the value of buttonGravity to Gravity.CENTER_VERTICAL ), and i push my code tohttps://github.com/lixi0912/ToolbarExpandHeightDemo
This is not a bug, just want to add a new feature.
In my case, i need to expand the height of the toolbar, and we want the menu button to be vertically in center of this toolbar, but buttonGravity api only accept Gravity.TOP or Gravity.BOTTOM, so we can only achieve it in a hack way ( set the value of buttonGravity to Gravity.CENTER_VERTICAL ), and i push my code to
vi...@google.com <vi...@google.com> #5
We have passed this defect onto the development team and will update this issue with more information as it becomes available.
Description
Version used: 1.1.0-alpha04
Theme used: Theme.MaterialComponents.DayNight.NoActionBar
Devices/Android versions reproduced on: android pie
- When I set toolbar_maxButtonHeight, since buttonGravity can only be set to top and bottom, it does not meet the CENTER_VERTICAL requirements of the design.