Open
Bug 1409974
Opened 7 years ago
Updated 2 years ago
KeyboardEvent.location could be used as a user behavior fingerprinting vector.
Categories
(Core :: DOM: UI Events & Focus Handling, enhancement, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
NEW
People
(Reporter: timhuang, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fingerprinting][fp-triaged])
Per Bug 1222285 comment 29, the keyboardEvent.location can be considered as a fingerprinting source of user behavior. I think we should find a way to address this issue. My proposal is that we could use a site permission. That's to say, we don't spoof the keyboardEvent.location if a user gives this permission. Otherwise, we spoof DOM_KEY_LOCATION_NUMPAD to DOM_KEY_LOCATION_STANDARD and DOM_KEY_LOCATION_RIGHT to DOM_KEY_LOCATION_LEFT.
|
||
Updated•7 years ago
|
Priority: -- → P2
|
||
Updated•6 years ago
|
Priority: P2 → P3
Whiteboard: [fingerprinting] → [fingerprinting][fp-triaged]
|
||
Updated•6 years ago
|
Whiteboard: [fingerprinting][fp-triaged] → [fingerprinting]
|
||
Updated•6 years ago
|
Whiteboard: [fingerprinting] → [fingerprinting][fp-triaged]
|
Assignee | |
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•