material-components / material-components/material-components-android

[AppBarLayout] WindowInsets are not correctly handled

Open
#2,120 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Widget: TopAppBar
Dominant language
Java
Stars
17.4k
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

**Description:** Inside a CoordinatorLayout, when using an AppBarLayout with fitsSystemWindows, the scrolling content is hidden by the keyboard (bottom inset).

**Expected behavior:** The scrolling content should be placed above the keyboard (bottom inset).

**Source code:** https://github.com/material-components/material-components-android/blob/master/testing/java/com/google/android/material/testapp/res/layout/design_appbar_toolbar_scroll_fitsystemwindows.xml (with an EditText using adjustResize)

**Android API version:** 33

**Material Library version:** 1.7.0

**Device:** Pixel 2

To help us triage faster, please check to make sure you are using the [latest version](https://github.com/material-components/material-components-android/releases) of the library.

We also happily accept [pull requests](https://github.com/material-components/material-components-android/pulls).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with testing/java/com/google/android/material/testapp/res/layout/design_appbar_toolbar_scroll_fitsystemwindows.xml and reproduce the AppBarLayout case with an EditText using adjustResize on Android API 33. Trace how the scrolling content responds to the keyboard bottom inset; done means the content remains above the keyboard while fitsSystemWindows is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.