Show keyboard on NTP show with native input

[malmstein]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1214157224317277/task/1214282876290070?focus=true

Description

When the native input field user setting is enabled, opening the NTP did not bring the keyboard up. The standard omnibar path worked because Command.ShowKeyboard calls showKeyboard() on the omnibar's text input; the native-input branch of the handler in BrowserTabFragment was a no-op.

This routes the command to showNativeInput() when native input is enabled, so the widget attaches and its existing onEnterComplete focuses the input — the same path that already works on a manual omnibar tap. The handler skips when the widget is already attached, since Command.ShowKeyboard can fire more than once per visit (e.g. CTA refresh) and showNativeInput() tears down and re-animates the widget on each call.

Steps to test this PR

Native input enabled

• Enable the native input field in settings.
• Open a new tab / NTP. The native input widget appears and the keyboard is up with the input focused.
• Cause a CTA refresh on the NTP — verify the widget does not flicker (no tear-down + re-animate).

Native input disabled (regression check)

• Disable the native input field.
• Open a new tab / NTP. The omnibar focuses and the keyboard appears, same as before.

UI changes

Before	After
(Upload before screenshot)	(Upload after screenshot)

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk UI behavior change limited to Command.ShowKeyboard, now surfacing the native input widget and avoiding repeated re-attach animations when the command fires multiple times.

Overview
Fixes NTP keyboard focus when native input is enabled by routing Command.ShowKeyboard to showNativeInput() (only if the widget isn’t already attached) instead of doing nothing.

Also includes minor Kotlin formatting/line-wrapping changes and a small command handler spacing tweak.

^{Reviewed by Cursor Bugbot for commit 9044bbc. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9044bbc. Configure here.}

[cursor]

Widget-attached check misses bottom omnibar variant

Medium Severity

The guard that prevents redundant showNativeInput() calls only checks for R.id.inputModeTopRoot, but when the omnibar is at the bottom (OmnibarType.SINGLE_BOTTOM), the widget is inflated with R.id.inputModeBottomRoot instead. For bottom-omnibar configurations, this findViewById will always return null even when the widget is already attached, defeating the guard entirely and causing the tear-down + re-animate flicker on every repeated Command.ShowKeyboard fire (e.g., CTA refresh). NativeInputManager.hideNativeInput and removeWidget both correctly check for both IDs — this check needs the same treatment.

 

^{Reviewed by Cursor Bugbot for commit 9044bbc. Configure here.}