Open Bug 1475551 Opened 4 years ago Updated 3 years ago

On GNU+Linux some pages "steal" the alt+1 hotkey so the Firefox hotkey alt+1 to switch tabs doesn't work anymore

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P5)

62 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: alexander.kern, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
Build ID: 20180709172241

Steps to reproduce:

Press alt+1 to switch tabs focus to first tab on GNU+Linux


Actual results:

Nothing, same tab is still focused. Maybe the page does something according to what it defines to happen when pressing alt+1


Expected results:

Firefox should have switched tab focus to the first tab.
Do you have an example of a page where this happens?

Any difference if you do the following on an offending site?
1. Click the icon on the left side of the address bar, which is either a circled (i) or a padlock.
2. In the panel that opens, click the > button, then the More Information button.
3. In the Page Info window that opens, click the Permissions tab.
4. Under "Override Keyboard Shortcuts" uncheck "Use Default", then select Block.


I suspect your other bug 1475550 is a duplicate of this: two effects of the same cause.
Blocks: 1052569
Component: Untriaged → Keyboard Navigation
See Also: → 1475550
Original page I was talking about has restricted access, users need to be registered, however I found this:
https://hosted.weblate.org/translate/androbd/fault-codes/en/?type=all&offset=3572
Alt+Home goes to your homepage, but doesn't work there because it has a page specific hotkey setting for that.

When I click the gear on the Permissions tab there is no "Override Keyboard Shortcuts" (it also says I have not granted this site any special permissions).

My other bug does not explain why Firefox doesn't execute what the shortcut should do, because it only also passes the input to the site. So if that were the same problem Firefox should execute what the Firefox shortcut should do and what the page's shortcut should do, right?

Hope that helps!
Your linked bug marked as blocking seems to be the same thing I'm looking for though, so I don't think this issue is needed anymore at least not for me. If it's useful to you of course, keep it. I'll post again if the other issue is fixed but not the GNU+Linux specific alt+... hotkeys. Thanks
(In reply to alexander.kern from comment #2)
> When I click the gear on the Permissions tab there is no "Override Keyboard
> Shortcuts" (it also says I have not granted this site any special
> permissions).

I didn't say to do that. Please read the directions at comment 1 again.
You're talking about the panel (doorhanger) of the address bar, not the Permissions sections of the Page Info window. You can also get there by right-clicking an empty area of the page and choosing View Page Info. Since sites can also disable the context menu, I described the address bar route instead.

(In reply to alexander.kern from comment #3)
> Your linked bug marked as blocking seems to be the same thing I'm looking
> for though, so I don't think this issue is needed anymore

Bug 1052569 doesn't seem to have a clear decision on which shortcuts should be protected. Looking at its list of dependencies, it seems to be used somewhat as a tracking bug. The people involved can mark this as a duplicate if they want, but marking this as blocking seemed like the right decision to me.
I'm sorry, you're totally right, clicked the wrong thing. Yes, blocking the keyboard shortcuts does get me the Firefox shortcuts back, awesome! Thank you for telling me about that useful feature, now I've got a quick fix :-) Should be reproducible for everyone on GNU+Linux on my given example page.

Okay, I just wanted to say I don't insist on this bug since the other one is enough for me already. Didn't want to propose anything.
Component: Keyboard Navigation → Event Handling
Product: Firefox → Core
Priority: -- → P5
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.