bug(windows): type `aa` gives output `aâ` instead of `â` in the Edge omnibar (formerly also in Chrome omnibar)

[MakaraSok]

Describe the bug

Per Dega keyboard rule, a + a = â, but when type aa in the Chrome omnibar on Windows, it instead outputs aâ.

Note that this does not happen when type in Chrome omnibar on macOS Big Sur.

To Reproduce

1. Go to 'Chrome'
2. Click on 'Omnibar'
3. Type 'aa'
4. See error

Expected behavior

All outputs should be consistent with the rules defined.

---

Keyman for Windows:

• OS: Windows 10 Pro 21H1 x64
• Keyman version: 14.0.274
• Target Application: Chrome Version 91.0.4472.77 (Official Build) (64-bit)

---

Keyboard

• Keyboard name: dega keyboard
• Keyboard version: 1.0
• Language name: Rade

Additional context

permalink: https://keyman.com/keyboards/dega#expand-languages

[ermshiperete]

I can't repro this with Chrome 105.0.5195.102 on Windows 10 (physical machine). Keyman 14.0.286 as well as 15.0.269.

@MakaraSok Can you retest this, please?

[rc-swag]

I can't repro this with Chrome 105.0.5195.102 on Windows 10 (physical machine). Keyman 14.0.286 as well as 15.0.269.

@MakaraSok Can you retest this, please?

Ok, so this also works for me on Chrome 105.0.5195.127 on Windows 10 and Keyman 16.0.47alpha (so not a release build) It works in Firefox. However, for Microsoft Edge version Version 105.0.1343.33 (Official build) (64-bit) it still has the reported problem but only for the first character pressed. I checked another keyboard with a rule and got the same result. It seems ominbar is causing focus to be lost after the first keypressed and the context is reset. In Summary: 1 . It is out of our control,

2. it now only occurs in Microsoft Edge but seeing as it is based on chromium it may soon bring in the change to fix.
3. It is only the first key pressed but works for every key after that so annoying but not too hard to deal with.