You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:NavigationView has logic to determine whether to display the insetForeground scrim in the bottom system window inset. This logic does not apply when android:theme is set for the view, as it is checking that the view's context is an instance of Activity, and setting a theme on the view replaces the context with a ContextThemeWrapper.
Expected behavior: When setting android:theme on a NavigationView with a non-transparent navigationBarColor applied to the window, the view should not draw insetForeground in the bottom system window inset area.
Source code: From NavigationView.java, in setupInsetScrimsListener:
If the Context is actually a ContextThemeWrapper or ContextWrapper instance, the logic is not performed and the view will draw the bottom inset foreground by default.
Android API version: 29
Material Library version: 1.2.0
Device: Pixel 2 XL
The text was updated successfully, but these errors were encountered:
Description:
NavigationView
has logic to determine whether to display theinsetForeground
scrim in the bottom system window inset. This logic does not apply whenandroid:theme
is set for the view, as it is checking that the view's context is an instance ofActivity
, and setting a theme on the view replaces the context with aContextThemeWrapper
.Expected behavior: When setting
android:theme
on a NavigationView with a non-transparentnavigationBarColor
applied to the window, the view should not drawinsetForeground
in the bottom system window inset area.Source code: From
NavigationView.java
, insetupInsetScrimsListener
:If the Context is actually a
ContextThemeWrapper
orContextWrapper
instance, the logic is not performed and the view will draw the bottom inset foreground by default.Android API version: 29
Material Library version: 1.2.0
Device: Pixel 2 XL
The text was updated successfully, but these errors were encountered: