Displaying the soft keyboard while in immersive full-screen mode doesn't function correctly.

Setting SYSTEM_UI_FLAG_FULLSCREEN | SYSTEM_UI_FLAG_HIDE_NAVIGATION | SYSTEM_UI_FLAG_IMMERSIVE_STICKY makes the status and navigation bars translucent and hides them. In this mode, swiping from the top or bottom of the screen temporarily displays the bars as described in https://developer.android.com/training/system-ui/immersive.html.

When in immersive mode, if the soft keyboard is displayed on the screen, the status and navigation bar translucency is removed and they are displayed. When the soft keyboard is closed, the status and navigation bars remain on the screen in their non-translucent state.

The expected behavior is either:

1 (preferred). When in immersive full-screen mode, displaying the soft keyboard does not display either the status or the navigation bar. When the keyboard is hidden immersive mode continues to work as before.

2. When in immersive full-screen mode, displaying the soft keyboard temporarily displays the status and navigation bars, leaving the status bar translucent if so set and temporarily setting an opaque background on the navigation bar. When the keyboard is hidden the status and navigation bars return to the state they were in before the keyboard was displayed.

Attached are four screenshots of a web browser built using WebView in immersive full-screen mode.

"Immersive Full-Screen Mode.png" shows Google's home page in immersive mode.

"Immersive Mode with Translucent Bars Displayed.png" shows the status and navigation bars temporarily displayed by swiping from the top of the screen. This is the expected behavior.

"Keyboard Breaks Immersive Mode.png" shows the keyboard breaking the translucent status of the status and navigation bars and forcing them to be displayed.

"Keyboard Leaves Immersive Mode Broken.png" shows that the keyboard leaves immersive mode in a broken state after it is hidden instead of returning it to the state it was in before the keyboard was opened.

This behavior has been observed on a Nexus 4 running 5.1.1, a Nexus 10 running 5.1.1, a Nexus 7 running 6.0.1, and a Nexus 6P running 7.1.1.