An AutoCompleteTextView should be used in the place of a TextInputEditText, along with with a Widget.MaterialComponents.TextInputLayout.(...).ExposedMenuDropdown style.
PiperOrigin-RevId: 246343749
Currently AppBarLayout lacks the functionality which
CollapsingToolbarLayout does, to draw a drawable behind
the status bar. This CL adds that functionality.
Also added related functionality to Catalog
PiperOrigin-RevId: 242949840
Caused by AppBarLayout + WindowInset commit, which breaks some incorrect
assumptions in CTL. Fixed by breaking apart ViewOffsetHelper
so that its tracking of layout coordinates, and applying
offsets, are done at different times.
Also fixed catalog's AppBar sample layouts to set IDs,
enabling state restoration to work.
PiperOrigin-RevId: 239592953
Now that there are a nice amount of text fields in the controllable text field demos, the controls are hidden in almost all cases. Splitting the icon text field demos into their own demos to avoid hiding the text field demo controls.
PiperOrigin-RevId: 239257310
This is pre-work for splitting the icon text fields into their own controllable demo screens. This commit:
- Adds an outline toggle password demo
- Removes unnecessary ids
- Reformats layout files
- Cleans up the demos
PiperOrigin-RevId: 239215370
The naming in spec changed for outlined text fields, and we changed the style name to reflect that a while back. This commit cleans up old references to "outline" text fields.
PiperOrigin-RevId: 239027786
For that reason, users should opt to use the start icon API instead of setting a start/left compound drawable on the text field's edit text.
PiperOrigin-RevId: 238984066
The catalog was setting the legacy bottom nav's android:background, which was overriding the background and ruining the contrast ratios.
PiperOrigin-RevId: 238539046
When AppBarLayout is used with a CollapsingToolbarLayout
child, it currently does not handle WindowInsets
very well. This commit fixes that by properly handling
insets.
The primary issue is when an AppBarLayout is used
with a single Toolbar (very common use case), where
the Toolbar will currently be displayed behind the status bar.
Another issue is with HeaderScrollingViewBehavior.
To workaround CoordinatorLayout using its 'compatible measuring'
for insets, the behavior manually sets the scrolling view to fit
system windows. This has other issues though because
that view will get padded in. Fixed by manually adding the insets
back into the measured dimensions.
Also updated the catalog layouts to make use of
android:fitsSystemWindows=true
Resolves https://github.com/material-components/material-components-android/pull/299
PiperOrigin-RevId: 238396626
