Support overriding existing keybinding through WebExtensions
Categories
(WebExtensions :: Frontend, defect, P5)
Tracking
(Not tracked)
People
(Reporter: Hi-Angel, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: triaged)
Updated•8 years ago
|
Comment 1•8 years ago
|
||
Updated•8 years ago
|
Comment 3•8 years ago
|
||
Comment 4•8 years ago
|
||
Updated•8 years ago
|
Updated•8 years ago
|
Comment 6•7 years ago
|
||
Comment 8•7 years ago
|
||
Comment 9•7 years ago
|
||
Comment 10•7 years ago
|
||
Comment 11•7 years ago
|
||
Comment 12•7 years ago
|
||
Updated•6 years ago
|
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
Comment hidden (advocacy) |
Comment 17•6 years ago
|
||
So, I found out about Saka-Key on this page https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly
I was trying to remap or disable Ctrl-Shift-C (I spend too much time copying stuff from the terminal and sometimes use it accidentally). I was unable to assign that shortcut to any other action in about:addons - Manage Extension Shortcuts, or with my own webextension, but for some reason Saka-Key manages to overwrite it. How?! This is exactly the use case in the title of this bug.
Updated•2 years ago
|
Comment 18•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 44 votes and 70 CCs.
:robwu, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Comment 19•2 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Comment 20•1 year ago
|
||
(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #18)
The severity field for this bug is relatively low, S3. However, the bug has 44 votes and 70 CCs.
:robwu, could you consider increasing the bug severity?For more information, please visit auto_nag documentation.
This page shows the definitions of all severities, and it says S3 is:
(Normal) Blocks non-critical functionality and a work around exists
I don't see any work arounds mentioned in this thread. Therefore, shouldn't it be changed to S2?
(Serious) Major functionality/product severely impaired or a high impact issue and a satisfactory workaround does not exist
Let me know if I misinterpreting the definitions (or being too pedantic, heh). Thanks!
Description
•