Chrome ignores keyboard locales
-
OK, so I'm doing some web dev and that occasionally means I'm attacking the DOM via the Inspector in Chrome to do things.
Now, I will 'fess up to being some level of because I'm doing this on a UK MacBook Pro (mine, I might add, as at the time I was freelancing and doing iOS stuff while still wanting to play games and stuff, so it's a decent 17")
The main thing this means... @ is shift-2, which it usually isn't on a UK keyboard. " is usually shift-2, and @ is shift-' (where ' is just next to ; on the home row)
I'm using the proper Apple layout so what's on my key-caps matches what's typed... except in Chrome. In the dev inspector, I type shift-2 and get " instead of @.
Then I realise it's happening in Chrome/Discourse editor as well. It's also happening in other Chrome tabs too.
Since my hard drive died a few months ago (it was 3 years old and heavily used!) I did a fresh install of everything including Boot Camp, and everything except Chrome adheres to the UK (Apple) keyboard layout. Everything open right now - Skype, Git-Bash, Notepad++, Firefox... but not Chrome.
Maybe Chrome is TR
-
I think you should be happy it lets you type at all.
It was created by a company that thinks there's no need to ask, if you're you want to close a window with those 100 tabs you've got open.
Oh, wait, that not true, they think that only Mac users might need this option and Windows (Linux too?) users should go
fuckfund themselves.
-
I'm running Chrome on Windows 7 on this MacBook... (I did say about gaming, because fuck Mac users if they want to play games)
-
Windows 7 on this MacBook
I'm surprised there isn't hardware bombs that check if Windows is running on their precious hardware and do crazy nonsensical stuff to fight it.
-
You mean like sending the wrong locale to chrome?
Filed Under: This wouldn't have happened on Linux hardware!
-
@Arantor said:
Windows 7 on this MacBook
I'm surprised there isn't hardware bombs that check if Windows is running on their precious hardware and do crazy nonsensical stuff to fight it.
They actually provide you a bundle to make it work easily. Complete with all the drivers and everything.
Except as I have the Late 2011 model, I'm one range behind the cut-off for Windows 10 drivers so that's not a thing either.
-
Found this...no idea if it will help. But you are not alone.
-
Interesting that it's a 6 year old regression.
That page also suggests there's a section in the Chrome settings where you can set 'encoding settings', and the help pages agree - except they haven't been updated in probably 20 versions.
Chrome, u y teh
-
-
-
If the 'Alt-Shift' suggestion fixed it, that's an OS-wide thing that changed per-application until Windows 8, where it's disabled by default in favor of Win-Space.
Not everything in newer Windows versions is worse.
-
Maybe Chrome is TR
Chrome on my Macbook Pro doesn't do this. It types the right characters for the layout.