We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description: The navigation rail applies start insets based on the system bars. This results in the rail appearing behind display cutouts.
Expected behavior: Apply start insets based on the display cutout
Source code:
material-components-android/lib/java/com/google/android/material/navigationrail/NavigationRailView.java
Line 216 in a2309ce
Minimal sample app repro: https://github.com/t895/yuzu/tree/material-update
Android API version: API 34
Material Library version: 1.10.0+ The bug was introduced with this commit
Device: Samsung Galaxy S21 and Google Pixel 7 both running their latest stable software updates as of 1/11/24
The text was updated successfully, but these errors were encountered:
Android: revert material to 1.9.0
ed69cc9
There's been an unresolved bug since version 1.10.0 Details: material-components/material-components-android#3990
7b25c1e
Successfully merging a pull request may close this issue.
Description: The navigation rail applies start insets based on the system bars. This results in the rail appearing behind display cutouts.
Expected behavior: Apply start insets based on the display cutout
Source code:
material-components-android/lib/java/com/google/android/material/navigationrail/NavigationRailView.java
Line 216 in a2309ce
Minimal sample app repro: https://github.com/t895/yuzu/tree/material-update
Android API version: API 34
Material Library version: 1.10.0+ The bug was introduced with this commit
Device: Samsung Galaxy S21 and Google Pixel 7 both running their latest stable software updates as of 1/11/24
The text was updated successfully, but these errors were encountered: