fix(android): sync upstream SystemBars fixes #8480 and #8481

[riderx]

What

Syncs two SystemBars fixes that are merged in ionic-team/capacitor but missing from plus:

• #8481 — respect insetsHandling: "disable"
• #8480 — show only the requested system bar

Plus one integration fix needed to make the two work together (details below).

Why

Both were carried by the stale upstream-sync branches, bundled with the "upstream-preferred fallback" resolution that renamed @capacitor-plus/* back to @capacitor/* and wiped the fork's changelogs. Stripping that damage from #71/#83/#85/#87/#88 also dropped these two genuine fixes on the floor. CodeRabbit flagged both as out-of-diff findings while reviewing #67, which is how they resurfaced.

They are worth having on their own merits:

• insetsHandling: "disable" did not work. Upstream fix(SystemBars): make safe-area-inset-x available on API <= 34 ionic-team/capacitor#8424 removed the insetHandlingEnabled guard, so the listener was installed and insets were rewritten regardless of config. chore: sync upstream PR #8454 - Fix navigation bar overlay in edge-to-edge mode on Android #67 restored the guard on the CSS injections; fix(SystemBars): respect insetsHandling disable ionic-team/capacitor#8481 finishes the job by returning early from initWindowInsetsListener, gating onDOMReady, and validating the config value with a warning on unknown input.
• Hiding the status bar also showed the navigation bar. setHidden(false, "StatusBar") called show(Type.systemBars()), which covers both bars. fix(android): show only the requested system bar ionic-team/capacitor#8480 narrows each branch to the bar actually requested and adds SystemBarsTest.

How

Cherry-picked d4ad7ff and 4c6c321 with git cherry-pick -x, preserving upstream authorship.

d4ad7ff conflicted with #67, which had just landed and reworks the same methods. Resolved by keeping #67's structure and layering ionic-team#8481's config handling on top:

• insetHandlingEnabled (boolean) becomes insetsHandling (String), with all five call sites migrated to INSETS_HANDLING_CSS.equals(insetsHandling).
• Kept chore: sync upstream PR #8454 - Fix navigation bar overlay in edge-to-edge mode on Android #67's ViewCompat.getRootWindowInsets(v) in initSafeAreaCSSVariables rather than upstream's WindowInsetsCompat.CONSUMED fallback, which yields zeros below API 35.
• Kept chore: sync upstream PR #8454 - Fix navigation bar overlay in edge-to-edge mode on Android #67's ViewCompat.requestApplyInsets(parentView) in onDOMReady over upstream's getBridge().getWebView().requestApplyInsets().

The third commit is a fork-specific integration fix. navBarVisible (added by #67) was only updated in the per-bar branches, but ionic-team#8480 restructured setHidden so bar.isEmpty() — the path initSystemBars uses for the hidden config — hides or shows every bar at once. With hidden: true the navigation bar was hidden while navBarVisible stayed true, so the API < 30 safe-area fallback reported a nav bar height for a bar that was not on screen. Upstream cannot have this bug because navBarVisible only exists here.

Testing

• bun run eslint and bun run prettier --check pass locally.
• SystemBarsTest.java comes from upstream fix(android): show only the requested system bar ionic-team/capacitor#8480 and runs in test-android.
• CI (setup / lint / test-cli / test-core / test-ios / test-android) runs on this PR.

Not Tested

• No on-device verification of insetsHandling: "disable", of hiding a single bar, or of the navBarVisible fix on an API < 30 device. All three are reasoned from the code and upstream's intent.

---

Opened by an AI agent (Cursor).

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 8 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: cba469b5-cf02-4b2b-9ed0-6ecf04d3096e

📥 Commits

Reviewing files that changed from the base of the PR and between 94d9f70 and 305095d.

📒 Files selected for processing (2)

• android/capacitor/src/main/java/com/getcapacitor/plugin/SystemBars.java
• android/capacitor/src/test/java/com/getcapacitor/plugin/SystemBarsTest.java

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Beta npm build

Maintainers can publish one Capacitor Plus workspace package from this PR to npm for fast testing.

Comment /publish-beta <package> after the PR checks are green.

Examples:

/publish-beta core
/publish-beta cli
/publish-beta @capacitor-plus/core

If exactly one workspace package changed, /publish-beta without a package will use that package.

Packages:

• core (@capacitor-plus/core)
• cli (@capacitor-plus/cli)
• android (@capacitor-plus/android)
• ios (@capacitor-plus/ios)

The workflow will:

• publish a prerelease package on the beta tag
• add a pinned pr-106 dist-tag for the selected package
• update this comment with the install command

Security note: beta publish is only enabled for branches inside this repository.

[cubic-dev-ai]

All reported issues were addressed across 2 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>