Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: