Open AlphaScorpii-dev opened 2 years ago
I wouldn't be at all surprised if this is a bug in the on-screen keyboard. I would suggest filing an upstream issue against ChromeOS.
https://github.com/GoogleChrome/developer.chrome.com/issues/250 is closely related.
Got the following feedback after raising the issue on the chromeos tracker.
3P inputs extensions need to provide their own Virtual Keyboard implementations that work alongside their Physical Keyboard IMEs, otherwise a fallback to a default US-Qwerty Virtual Keyboard is used, which may not be ideal or may not even work properly at all. In this case, it's highly likely that the mentioned 3P extension doesn't provide a Japanese-layout based Virtual Keyboard. Therefore, this looks like things are working as intended, hence I'm closing this bug as such.
Now, I’m not really familiar with Chrome extensions, but I didn’t see anything related to virtual keyboards in the Compose Key one. Does this mean that US and UK virtual keyboards are identical on screen ? I assumed changing the layout would be enough to modify the virtual keyboard as well.
@AlphaScorpii-dev please could you share a link?
I have modified a little the original compose-key in order to be able to use it with my japanese chromebook. It works great as long as I am on the physical keyboard, but I have noticed that when I go into tablet mode, I always get an american layout displayed on the on-screen keyboard, while the pressed key is indeed mapping the japanese layout correctly. This is how I changed the manifest, but perhaps I am missing something so the on-screen keyboard is displayed correctly?