Closed Bug 1938109 Opened 2 months ago Closed 2 months ago

Fenix browser should not be resized by default when IME is shown to support the interactive-widget meta tag

Categories

(Fenix :: Browser Engine, task)

All
Android
task

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: petru, Unassigned)

References

Details

Based on the proposal for the browser following the soft-input mode specified by websites through the interactive-widget meta tag
And the implementation for GeckoView from bug 1831649
It seems like Fenix should by default do nothing when browsing and the IME is shown to support websites' content being shown underneath the soft keyboard.
Currently by default the app's viewport will be resized to be shown on top of the soft keyboard based on the AndroidManifest configuration.

@Hiro Are my assumptions correct?
Should Fenix stop resizing the engine View when dom.interactive_widget_default_resizes_visual is enabled?

Flags: needinfo?(hikezoe.birchill)
Flags: needinfo?(hikezoe.birchill)

(In reply to Hiroyuki Ikezoe (:hiro) from comment #2)

No. Rather it should set. See https://hg.mozilla.org/integration/autoland/rev/bfbf94d9ecbc .

But wouldn't this mean that we can't support overlays-content since based on that manifest property the activity will automatically be resized to above the keyboard?
Or is this already accounted for in GeckoView?

Want to know this for sure because on Android 15 apps are by default edge-to-edge and since we don't want that we have to apply the systembars insets ourselves manually and then for bug 1917818 we have to basically support adjustResize ourselves to be able to sync the toolbar to be shown on top of/animated together with the IME - can do it but after reading about overlays-content I'm not sure we should.

The activity window gets resized, but each web content window doesn't get resized, that's what we did in bug 1831649. The main part of the change is https://hg.mozilla.org/integration/autoland/rev/8b197fb54abc. If you are interested, I'd suggest you to look all changes in bug 1831649.

And I believe Chrome does the same thing, at least last time I checked their code.

Sounds good to me, thanks!

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.