Compose for Web: Initial IME support

[jershell]

Proposed Changes

This PR is an attempt to provide basic support and accumulate knowledge about the state of affairs with keyboard (ime) in mobile web browsers

Testing

chrome on mobile device - ok
safari on mobile device - ok

Test:
Desktop browsers are not affected.
On mobile devices the keyboard is visible and works =\

Google CLA

OK

Working demo

Screenrecorder-2024-02-08-18-26-48-399.mp4

Demo problems

Screenrecorder-2024-02-08-18-27-39-629.mp4

Comments

`<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=0">`

user-scalable=0 set to 0 to prevent default zoom in safari browser

Limitations

• Bad text selection
• Context menu.

Note

Based on the information at this time, several implementation options are likely.

• By precise positioning, highlight content inside html input, provoking the browser to show the system context menu.
• Implement the context menu by compose.

• Poor positioning to focused input.

Note

The keyboard changes the current viewPort, which does not work exactly, perhaps on google chrome you can use https://developer.chrome.com/blog/viewport-resize-behavior, but it is not clear what to do with safari

• safari doesn't show keyboard when clicking on focused TextField again.

Additional. Why is the VirtualKeyboard API not used.

Summary of the VirtualKeyboard API https://w3c.github.io/virtual-keyboard/ at 2024

• Specification being incubated in a Community Group
• support is only available in chrome,
• unsupported in firefox
• unsupported in safary
• requires an HTML element with the contenteditable and virtualkeyboardpolicy="manual" attributes.
• There are problems and questions regarding use (https://github.com/w3c/virtual-keyboard/issues)

Note

browser_compatibility

[jershell]

@eymar Hello. Can you help me with this PR?

[jershell]

@eymar Hello, is there any news on my PR?

[eymar]

Hi @jershell ! Thanks for a ping. The feature you implemented is really important and we appreciate your contribution :)

We would like to carefuly evaluate this solution with its nuances and the possible alternatives if they are necessary.
Currently, the team is preparing (planning) for the next milestone. We'll make sure this feature is included.
That means we'll review this PR properly a bit later.

[jershell]

@eymar Hello, any news?

[eymar]

@eymar Hello, any news?

No news yet :)
We will not forget about this PR - I can promise that. This feature is a must-have for 1.6.10 release.

[jershell]

I pulled latest master. Now we have a bug. The click does not hit on widget. I mention that the bug is not mine -_- and the keyboard works, you just need to press higher (about 50-60dp).

[jershell]

@eymar Hello. I see version 1.6.10*** got it. Does this mean that we can soon merge this PR?

[ismai117]

@jershell does the keyboard now show up if I use v1.6.10-dev1551?

[jershell]

@jershell does the keyboard now show up if I use v1.6.10-dev1551?

no, only after the merger

[jershell]

@eymar hi, any news?

[eymar]

@eymar hi, any news?

@Schahen is working on this topic (related parts).

[Schahen]

@jershell Hi jershell, I'd had to recompose you PR due to the changes in our event-related approach in general, but don't think that your contribution is wasted - it's actually quite the opposite, we've based our changes on the work you provided (and make sure that the authorship will be preserved in the final merge that's yet to be)

you can check #1259 for further progress
this PR I am closing.