this post was submitted on 22 Jul 2024
14 points (100.0% liked)
LibreWolf
3133 readers
1 users here now
Welcome to the official community for LibreWolf.
LibreWolf is designed to increase protection against tracking and fingerprinting techniques, while also including a few security improvements. LibreWolf also aims to remove all the telemetry, data collection and annoyances, as well as disabling anti-freedom features like DRM. If you have any question please visit our FAQ first: https://librewolf.net/docs/faq/
To learn more or to download the browser visit the website: https://librewolf.net/
If you want to contribute head over to our Codeberg: https://codeberg.org/librewolf
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I dug into the code and tested again, and it appears that this bug/issue is actually around the
event.shiftKey
which registers astrue
in librewolf when the caps lock key is on, and shift is not pressed, and will register as false if the caps lock key is on, but shift is also on. Firefox on the other hand will register the event.shiftKey status as true/false simply based on whether the shift key is down or not, which is what I would generally sxpect from the browser.In case it helps, the code in question is below:
This way, it checks for lower or uppercase S (83/115) and if the shift key is down. Thus the post will save with the shift+s key, no matter what state the caps lock key is in (in Firefox/chrome). However in librewolf, because the shift key is tied simply to capitalization (combos of shift and caps lock), if you just type a captial S, the save post functionality will trigger.
Huh. Cool.
Not a dev; honestly I’d have thought the OS would have more control over that than LW.
TIL. Good luck 👍