1708095 - Hamburger menu in combination of keyboard shortcut

Status: NEW

(Firefox :: Keyboard Navigation, defect, P5)

Description

[Peter deHaan [:pdehaan]]

This comment is copy/pasted from a community issue filed during the Foxfooding program.

NOTE: This issue was translated from Spanish to English via Google Translate.

---

Firefox Version: Mozilla / 5.0 (Windows NT 10.0; Win64; x64) AppleWebKit / 537.36 (KHTML, like Gecko) Chrome / 90.0.4430.93 Safari / 537.36
Window Size (inner width and height): 1536x698

Steps to Play

A) Hamburger Menu
2) Press Ctrl + shift + P - stay in the same window
3) Pressing Ctrl + shift + A stays in the same window
4) Pressing Ctrl + shift + Q stays in the same window

Expected Behavior

Pressing keyboard combination: Ctrl + Shift + P should show me a private new window.
Pressing keyboard combination: Ctrl + Shift + A was supposed to show me the sale of plugins and themes.
Pressing keyboard combination: Ctrl + Shift + Q should close the sale

Current Behavior

Running the keyboard shortcut does not make the change for every keyboard combination.

Comment 1

[Peter deHaan [:pdehaan]]

Attachment: User screenshot

Comment 2

[Luca Greco [:rpl] [:luca] [:lgreco]]

I'm pretty sure that this kind of issue may be reproduced if:

• the tab content being focused
• and the webpage loaded in that tab is handling keyboard shortcuts using regular WebAPI

e.g. if you have slack opened in a tab and the focus is currently on that tab, Ctrl-Shift-A is intercepted by slack, which binds it to selecting the "All unread" sidebar entry.

On slack the behavior is pretty visible because the shortcut is also affecting what slack does render, but on other webpage that may not be that visible, and that would explain the reason for reporting this (even if it is kind of expected).

Unfortunately the report doesn't explicitly mention what was loaded in the tab and it cannot be guessed based on the attached screenshot,
without more details this is very likely not actionable and we may have to close it as incomplete if we don't have any way to get some more details to complete the STR.

I really doubt this is proton related, as far as I remember this was already happening before proton.

Comment 3

[Romain Testard [:RT]]

Agreed, not able to reproduce here on Win10

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:dao, could you have a look please?

For more information, please visit auto_nag documentation.