Recently, there is regression in Google Chrome, in which the browser ignores some XKB keymap layouts.
This was caused by upstream implementing input methods directly into Chromium/Chrome for the purposes of ChromeOS, circumventing the X11 xkb extensions. Specifically the use of keymap whitelist which ignores any layouts not listed.
Revelant chromium issues/tasks:
Unfortunately, there is nothing I can do about it.
In the meantime, layouts will be migrated to ibus where possible. This involves activating them in ibus and adding a rule in jbxkb.
Recently, there is regression in Google Chrome, in which the browser ignores some XKB keymap layouts.
This was caused by upstream implementing input methods directly into Chromium/Chrome for the purposes of ChromeOS, circumventing the X11 xkb extensions. Specifically the use of keymap whitelist which ignores any layouts not listed.
Revelant chromium issues/tasks:
Unfortunately, there is nothing I can do about it.
In the meantime, layouts will be migrated to ibus where possible. This involves activating them in ibus and adding a rule in jbxkb.