New issue
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
Taginput and cyrillic symbol "б" #1485
Comments
Большинство компонентов написано фиг пойми как и не тестируются меинтейнером, при этом багфиксы без объяснений - не принимаются. Привыкай. |
@jtommy maybe you should merge it? I already tested. |
@service-paradis create pr with this fixes, coz @jtommy take some drugs and started do some stupid things again, xD. |
In fact, we would need to rewrite some component events that are using the deprecated KeyCode The problem with KeyboardEvent.key right now is to support IE11 that uses an early version of the spec (for example, it uses "Esc" rather than "Escape"). Not a hard job, but would need to verify every key used to be sure to support IE (by using There is also an open issue because it does not always work when combining keys (https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/742263/). I also got an issue when using comma. IE11 is sometimes returning me "Decimal" instead of "," since the decimal separator for french canadian is a comma. So, the commit you made is probably a good start but wont work for any cases. Fortunately, there is a great guide with all the keys and exceptions. Would need to make a lot of tests using different browsers to be sure to be compatible. |
We can just create some array of keycodes and other stuff like that, and create some handler inside https://github.com/buefy/buefy/tree/dev/src/directives dir and that's all. So, i can confirm that's not IE bug, this is normal behavior for Windows(testsed on some c++ stuff). Also from link that you given, they wont fix it, coz seems like that's not bug. |
@jtommy It would be a breaking change in some component where we can define key codes in prop (TagInput for example). So maybe we could label this issue as |
Sure! |
we should make more brekabke changes with fixes since 0.7.x in 0.9 release. |
maybe add a property to the component that blocks comma processing, |
In the next breaking release, we will cange the way Buefy handles Key events. It will solve this problem without the need to add a new prop. |
Overview of the problem
Buefy version: 0.7.7
Vuejs version: 2.6.10
OS/Browser: Mac OS
Description
In the Cyrillic keyboard layout (for example in the Russian language) to type letter
б
you should press the same button that types,
in the Latin layout (keycode: 188). After pressing this button in the taginput component, I expect to see the typed letter in the default behavior (without overridingconfirmKeyCodes
) but actually got confirmed tag.In the Cyrillic layout, pressing Shift+6 causes typing a comma, but I would expect to see the confirmed tag.
As a solution, we can handle the
keypress
event in combination withkeydown
.keypress
event has information about char code, whereб
and,
have different codes.Steps to reproduce
confirmKeyCodes
:P.S. It's not duplication of #1148
The text was updated successfully, but these errors were encountered: