privacy.resistFingerprinting breaks extension shortcuts using 'Alt'
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
People
(Reporter: m, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Steps to reproduce:
- Create new profile
- Install an extension. I'll use DarkReader as an example, but this applies to all extensions.
- Define a shortcut for the extension (in about:addons -> Manage Extension Shortcuts) which uses the 'Alt' key. DarkReader has 'Shift+Alt+D' as a default shortcut.
- Visit some page, confirm that 'Shift+Alt+D' works.
- Set 'privacy.resistFingerprinting' to 'true'
- Press 'Shift+Alt+D'.
Actual results:
Nothing, the extension does not register the shortcut.
Expected results:
Same behaviour as 'privacy.resistFingerprinting = false'
|
||
Comment 1•5 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Privacy: Anti-Tracking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•5 months ago
|
||
It's possible this is expected behavior, as RFP does spoof the keyboard layout, which can mess with modifier keys. Can I ask what locale and keyboard layout you are using?
I would also be curious to know if you put focus in a browser chrome part (like maybe about:preferences) and try it there to see if it works.
I tried reproducing this again, and found that I can't reproduce the behaviour in the way I described it.
The shortcuts only doesn't work if the vimium extension is installed as well.
I'm guessing I must have tried both extensions during my first tests, and that this is a case of vimium not being able to handle the spoofed modifier keys.
I found this issue in the vimium repo:
https://github.com/philc/vimium/issues/4053
which links back to
https://bugzilla.mozilla.org/show_bug.cgi?id=1536533
which was closed as INVALID as this is the intended behaviour.
Shortcuts in about:preferences work fine.
|
||
Comment 4•5 months ago
|
||
Note that Bug 1536533 doesn't describe exactly the same Bug, we could potentially spoof the keyboard events to the website, but give extensions all keyboard events. However, I don't know how whether the complexity would be worth the usability gain.
Description
•