It is not possible to enter the euro sign and the at sign using the on-screen keyboard (UWP-App)

[agenne]

Hello,
after weeks we finally managed to convert our SelfService app to WebView2.
Unfortunately, during the integration test, it was noticed that entering the euro sign (€) and the at sign (@) on the on-screen keyboard is not possible.

With this we cannot use the WebView2.

The problem can be easily reproduced with the webview2_sample_uwp. And we could reproduce the problem on each of our computers.

The problem does not occur in a WPF application with WebView2. So it seems to be a UWP issue.

System:

Windows 10 22H2 Build 19045.2193
Edge: 107.0.1418.26
User Agent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36 Edg/107.0.1418.24'

The bug was noticed on a system with German layout. After installing an english Keyboard the behavior is changing but is also wrong. Some characters, especially selected from flyouts, are inserted twice. The euro sign is also inserted twice. Apart from this, it is not an option for us, to use the english keyboard layout.

We request a fix for this bug with very high priority.

Thanks in advance

AB#43486548

[agenne]

Hello,
is there any progress on this issue?
Any idea how long it takes to fix the problem?
Best Regards

[btmpn]

We are facing the same issue. Are there any news on this?

[agenne]

Again the request for information about the progress. Is there any hope that the problem will ever be solved? The bug was posted more than a month ago and there is no feedback whatsoever!

[Anderske]

We are facing the same issue. Please update status.

[btmpn]

Hello @nishitha-burman you assigned this issue to @tofuandeve, but obviously several months have passed without a response. Can we expect any feedback or even a solution here?

[tofuandeve]

Hi, I can repro this on windows 10, webview2 runtime v111. I'll open a bug and we'll start looking into this issue.

Thanks!

[agenne]

Hi @tofuandeve, hi @nishitha-burman,

is there any progress on this issue?
Any idea how long it takes to fix the problem?

[axert]

Hi, everyone.

Are there any updates, a timeline?

Many thanks,
A.