[dkersten]

It doesn't appear to respect my keyboard layout - I'm using colemak (which works fine) but with UK symbols instead of US (which works everywhere else, including the HN comment box, but not in Typing.io where it wants me to type US symblos: eg " and @ are swapped).

[ZoFreX]

I can't type underscore on my "British" layout MBP keyboard.

I wrote a typing tutor a while ago and this is a somewhat common pitfall, to manually handle characters by pulling key codes. Instead you should let the O/S tell you which character was typed (and also check key codes, for things like backspace) which then handles different layouts / locales etc.

Edit: Ok, it works in Chrome - so it's not working for me in Firefox 14.0.1 on OS X Lion.

Now that I can use it, I love it, but I have one request - I'd like to be able to go back and see my stats, please!

[jfaucett]

yea, german keyboard here and it doesn't recognize my "=" ( so couldn't get past line one. Looks really cool though, I hope it gets I18lized sometime soon :)

KeyboardJS has a basic locales mapping: https://github.com/RobertWHurst/KeyboardJS , Unfortunately it appears to only have en_US at the momment though

[ahnberg]

Unfortunatelly suffering from the same problems, as soon as I type : or ( or = or anything other than normal characters, I get errors. :( Cool typing experience other than that!

[minikomi]

Japanese keyboard user here.. I'm sure that ( is above the 8 :)

[pimentel]

Yeah. On a portuguese layout, doesn't recognize the "=" character. Problem with other characters as well...

This on Firefox 14, Chromium 18, Opera 12, for Linux Mint.

Otherwise, this is great!

EDIT: Does it read the key-code, instead of the character? Is it not possible to listen for the character input?

[ThomasQue]

Same problem with fr_FR on an azerty keyboard (Ubuntu or Windows 7). For example I can only type </> by typing <:> instead of the correct <shift> + <:>. For a <$> I would type <shift> + <'>.

It occurs both in Chrome and Firefox.

[ThomasQue]

This seems partially fixed. Though I cannot find a way to type <^>. On my azerty keyboard, I should type <^>+<^>, or on a querty one, simply <shift>+<6>, but neither works.

[pgsandstrom]

Same here. I'm using swedish layout, and it could not recognize semicolon

It wasn't even enough to press the corresponding button where semicolon is placed on English layout, I had to actually switch keyboard-layout and then press the correct button to get past it.

[tbrownaw]

Can't type underscore at all, have to use the numpad to type dashes. If I have the layout set to US-International, I have to type alt-shift-doublequote to get "; it won't let me type shift-doublequote and then the next character (or space) like normal. CapsLock doesn't seem to work, so for some of the identifiers in the C++ example I need to hold down shift for a half-dozen letters in a row.

[zcid]

I have the same issues using US International on OSX 10.6.

[albertoavila]

Same here with latam keyboard layout, the problem seems to be on every symbol on the keyboard number row, ej. =, /, &, etc.

[Inetgate]

I have also same issue with Dell's USB keyboard for Japanese language. For example, that site can't detect "=", "_", etc...

[Flenser]

At least they're just swapped. I don't know where it thinks " is on my keyboard :(

[ibotty]

strange. i have no problems whatsoever regarding keyboard layout. and i am using an obscure one. is this os-dependent in a way? (i'm just curious and want to understand the problem)

[dkersten]

Chrome on Windows 7 64bit does what I explained above. Chromium on Arch 64bit works fine.

In windows, I made my own keyboard layout in Microsoft Keyboard Layout Creator (so that I could switch the symbols to UK but also so I could add some dead keys to AltGr for various unicode symbols). I did "fix" the VK codes for the alphabethic characters, but I guess the symbols are still using whatever the key is assigned by default and I guess JS (at least in Chrome on Windows 7) checks the key code reported by the OS, rather than the value reported by the OS.

On Arch I use the GB colemak layout that came with the distro and I guess it sets all the key codes correctly to where all the symbols are...