Skip to content

fix: [SDK-5198] keep the system navigation bar visible for HTML in-app messages - #2767

Open
abdulraqeeb33 wants to merge 1 commit into
mainfrom
ar/sdk-5198
Open

abdulraqeeb33 wants to merge 1 commit into
mainfrom
ar/sdk-5198

Conversation

@abdulraqeeb33

@abdulraqeeb33 abdulraqeeb33 commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Description

One Line Summary

Full-bleed HTML in-app messages no longer hide the Android system navigation bar.

Details

Motivation

On Android, an HTML in-app message hid the system navigation bar for as long as it was showing. The activity's navigation inset collapsed, so an app bottom bar laid out from that inset shifted down. Dismissing the message restored both. Block Editor messages were unaffected because they are not full bleed.

Full-bleed WebViews requested SYSTEM_UI_FLAG_HIDE_NAVIGATION and SYSTEM_UI_FLAG_IMMERSIVE. They now request layout flags only, so the message still draws behind the bar and the bar stays visible.

Scope

Applies to full-bleed in-app messages (remove_height_margin), which is how HTML Editor messages are sent. Messages with margins are unchanged. The bottom edge of a full-bleed message can sit under the visible system bar. HTML that honors setSafeAreaInsets can pad for that.

Testing

Unit testing

WebViewManagerDismissCleanupTests asserts a full-bleed WebView does not set SYSTEM_UI_FLAG_HIDE_NAVIGATION or SYSTEM_UI_FLAG_IMMERSIVE, and still sets the layout-behind flags. Dismiss cleanup is unchanged.

Manual testing

HTML Editor message, edge-to-edge red page, 3-button navigation, demo app on an emulator.

Before: the three buttons disappear while the message is up.

Before: system navigation buttons are hidden

After: the three buttons stay on the white bar.

After: system navigation buttons stay visible

Affected code checklist

  • Notifications
    • Display
    • Open
    • Push Processing
    • Confirm Deliveries
  • Outcomes
  • Sessions
  • In-App Messaging
  • REST API requests
  • Public API changes

Checklist

Overview

  • I have filled out all REQUIRED sections above
  • PR does one thing
  • Any Public API changes are explained in the PR details and conform to existing APIs

Testing

  • I have included test coverage for these changes, or explained why they are not needed
  • All automated tests pass, or I explained why that is not possible
  • I have personally tested this on my device, or explained why that is not possible

Final pass

  • Code is as readable as possible.
  • I have reviewed this PR myself, ensuring it meets each checklist item

… HTML in-app messages

Hiding the bar collapsed the activity insets and shifted the host app's own bottom bar.

Co-authored-by: Cursor <cursoragent@cursor.com>
@abdulraqeeb33
abdulraqeeb33 requested a review from a team as a code owner September 25, 2026 14:42
@github-actions

Copy link
Copy Markdown
Contributor

📊 Diff Coverage Report

Diff Coverage Report (Changed Lines Only)

Gate: aggregate coverage on changed executable lines must be ≥ 80% (JaCoCo line data for lines touched in the diff).

Changed Files Coverage

  • WebViewManager.kt: 2/2 touched executable lines (100.0%) (6 touched lines in diff)

Overall (aggregate gate)

2/2 touched executable lines covered (100.0% — requires ≥ 80%)

📥 View workflow run

@abdulraqeeb33 abdulraqeeb33 self-assigned this Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant