View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0030204||Runner||HTML5||Public||2018-11-12 17:07||2019-05-13 17:35|
|Reporter||Stewart Bishop||Assigned To||Mike Dailly|
|Priority||Low||Severity||C - General||Reproducibility||100%|
|Target Version||2.2.1||Fixed in Version||2.2.1|
|Summary||0030204: HTML5: keyboard_string and keyboard_lastchar translate key presses as if the keyboard in use was a UK keyboard|
|Description||Under HTML5, the built-in variables keyboard_string and keyboard_lastchar translate key presses as if the keyboard in use was a UK keyboard.|
For instance, on my US keyboard Shift-2 would produce @ but instead I get ". There are number of inconsistencies like this that point to this US keyboard acting like a UK keyboard.
Chrome, Firefox, and Edge all act the same.
Internet Explorer 11 works as expected.
|1.4 Found In|
|2.x Runtime Found In||126.96.36.1997|
|2.x Runtime Verified In||188.8.131.527|
keyboard_string.yyz (20,060 bytes)
This is working as expected. However, you will need the correct language+region packs installed along with the correct keyboard installed and active. Installing both a US and UK region packs I was able to swap between them using the taskbar's language settings, and once this is done the keyboard input in the test app works as expected.
I suspect that browsers use the current language setting to help determine keyboards etc. We can only pass on what the browser tells us in these cases I'm afraid.
|Turns out this only happens when the code is obfuscated so we're reopening this.|
|Fixed the obfuscation of the "key" inside the keydown event. Should now work as designed.|
||Fix is in runtime 282+.|