Skip to content
New issue

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

[NavigationRailView] Start insets use the system bars instead of the display cutout #3990

Open
t895 opened this issue Jan 11, 2024 · 0 comments · May be fixed by #3991
Open

[NavigationRailView] Start insets use the system bars instead of the display cutout #3990

t895 opened this issue Jan 11, 2024 · 0 comments · May be fixed by #3991

Comments

@t895
Copy link

t895 commented Jan 11, 2024

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:

ViewUtils.isLayoutRtl(view) ? systemBarInsets.right : systemBarInsets.left;

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

@t895 t895 added the bug label Jan 11, 2024
rtiangha added a commit to rtiangha/Lime3DS that referenced this issue May 24, 2024
There's been an unresolved bug since version 1.10.0
Details: material-components/material-components-android#3990
OpenSauce04 pushed a commit to Lime3DS/Lime3DS that referenced this issue May 25, 2024
There's been an unresolved bug since version 1.10.0
Details: material-components/material-components-android#3990
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants