3 ms·
You probably don't want web pages seeing that you use a numpad for typing numbers anyway. It's just another fingerprinting vector.
by dexterdog 2y ago
You probably don't want web pages seeing that you use a numpad for typing numbers anyway. It's just another fingerprinting vector.
- slig 2y agoHow would the browser even know that, since the keyboard is sending the different codes over the wire.
- zamadatix 2y agoYou've pretty much dug out your own answer: The browser exposes both event.key and event.code in the keypress event. If it didn't life would be pretty miserable for interactive content expecting positional things like wasd.
- slig 2y agoThe parent of the comment I replied said that their kb lies about the key being pressed, so there's no way for the browser to know and fingerprint the user as the comment I replied implied.
- creesch 2y agoTell me you haven't read the article without telling me you haven't read the article ;) Not only does your browser know the character code, it knows the key that is pressed. For details I do recommend reading the article itself.
- slig 2y agoI did read the article. The parent of the comment I replied to said that their keyboard lies about the key being pressed.