Skip to content
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

BREAKING: Use KeyboardEvent.key instead of keyCode #1940

Merged
merged 4 commits into from Apr 24, 2020

Conversation

service-paradis
Copy link
Collaborator

@codecov
Copy link

codecov bot commented Nov 1, 2019

Codecov Report

Merging #1940 into dev will increase coverage by 0.25%.
The diff coverage is 63.15%.

Impacted file tree graph

@@            Coverage Diff             @@
##              dev    #1940      +/-   ##
==========================================
+ Coverage   65.19%   65.44%   +0.25%     
==========================================
  Files          71       71              
  Lines        2945     2952       +7     
  Branches      980      956      -24     
==========================================
+ Hits         1920     1932      +12     
+ Misses        947      942       -5     
  Partials       78       78
Impacted Files Coverage Δ
src/utils/TimepickerMixin.js 43.27% <0%> (ø) ⬆️
src/components/datepicker/Datepicker.vue 68.96% <0%> (-0.4%) ⬇️
src/components/dropdown/Dropdown.vue 55.85% <100%> (+3.12%) ⬆️
src/components/modal/Modal.vue 81.69% <100%> (+1.69%) ⬆️
src/components/sidebar/Sidebar.vue 64.1% <100%> (+6.2%) ⬆️
src/components/navbar/NavbarItem.vue 85.71% <100%> (+0.71%) ⬆️
src/components/loading/Loading.vue 90% <100%> (+3.79%) ⬆️
src/components/taginput/Taginput.vue 30.76% <33.33%> (-0.4%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 21174d1...dcf7db6. Read the comment docs.

@afwn90cj93201nixr2e1re
Copy link
Contributor

I think we should discuss using key.code too. What do you think about it?

@service-paradis
Copy link
Collaborator Author

Maybe. Right now, I dont know in which case it would be useful. https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code

Since the physical key can be really different between different keyboard (AZERTY vs QWERTY for example)

This property is useful when you want to handle keys based on their physical positions on the input device rather than the characters associated with those keys; this is especially common when writing code to handle input for games which simulate a gamepad-like environment using keys on the keyboard. Be aware, however, that you can't use the value reported by KeyboardEvent.code to determine the character generated by the keystroke, because the keycode's name may not match the actual character that's printed on the key or that's generated by the computer when the key is pressed.

@jtommy jtommy added this to To do in v1 Apr 8, 2020
@jtommy jtommy merged commit 50383ab into buefy:dev Apr 24, 2020
@jtommy jtommy moved this from To do to Done in v1 Apr 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
v1
  
Done
Development

Successfully merging this pull request may close these issues.

Taginput: Error when pressing russian letter "Б" on entering tags Taginput and cyrillic symbol "б"
3 participants