Open Bug 1625784 Opened 4 years ago Updated 4 years ago

Unable to use "e" accesskey on macOS [ctrl-alt-e] [⌃⌥e]

Categories

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

74 Branch
Unspecified
macOS
defect

Tracking

()

People

(Reporter: krinkle, Unassigned)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [platform-rel-Wikipedia] )

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

  1. Navigate to https://en.wikipedia.org/wiki/Wikipedia:Sandbox in latest Firefox on macOS.
  2. Hover the "Edit" button, and observe its access key label [⌃⌥e], in other words [ctrl-alt-e].
  3. Perform the keyboard shortcut.

Actual results:

Nothing.

Expected results:

It should have performed a navigation to the Edit anchor link's href.

This problem appears to be specific to the access key "e". Other letters on the same page work fine. Such as "h" to go to the History tab, or "k" to go to the Recent changes page, or "f" to Find something via the search input field.

I suspected if maybe the keyboard shortcut was taken by something native, but was unable to find anything. Also nothing else outside or inside the browser happened instead of the expected action.

The combination in question is advertised by Gecko via node.accessKeyLabel.

Component: Untriaged → DOM: UI Events & Focus Handling
Product: Firefox → Core

Can you take a look? Thank you.
Not sure if this is a recent regression. Impacting wiki editing sounds concerning.

Flags: needinfo?(echen)
Attached file test.html

Here is simplified test script.

This doesn't look like a regression, I could also reproduce on 57.
And look liks a Mac-specific bug given that I could not reproduce on Windows.

OS: Unspecified → macOS

(In reply to Edgar Chen [:edgar] from comment #2)

This doesn't look like a regression, I could also reproduce on 57.

Hmm, I could not reproduce on 52, so it might be a regresssion between 52 ~ 57.
mozregression-ing...

10:36.89 INFO: Got as far as we can go bisecting nightlies...
10:36.89 INFO: Last good revision: e91de6fb2b3dce9c932428265b0fdb630ea470d7 (2017-03-02)
10:36.89 INFO: First bad revision: 9732cd019a8b94c49a275661320c1b742635a3d6 (2017-03-03)
10:36.89 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e91de6fb2b3dce9c932428265b0fdb630ea470d7&tochange=9732cd019a8b94c49a275661320c1b742635a3d6

Flags: needinfo?(echen)

Might be related to Bug 1343446 or Bug 1342865.

I tried to get regression window by mozregression, but it stopped at https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e91de6fb2b3dce9c932428265b0fdb630ea470d7&tochange=9732cd019a8b94c49a275661320c1b742635a3d6 with following warning,

11:28.93 INFO: There are no build artifacts for these changesets (they are probably too old).

Alice, is it possible that we could get a more accurate regression-window? Thanks

Flags: needinfo?(alice0775)

This seems to be Mac specific. Sorry, I do not have a Mac.

Flags: needinfo?(alice0775)

Daniel, do you know if it is possible that we could get a more accurate regression-window? Thanks.

Flags: needinfo?(daniel.bodea)

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression

There seems to be a problem with mozregression on older OSes. Finding someone else to attempt it.

Flags: needinfo?(daniel.bodea) → needinfo?(peter.magyari)

Hi,

I've tried to get a more accurate regression range but I got the same results as Edgar.
It stopped at https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e91de6fb2b3dce9c932428265b0fdb630ea470d7&tochange=9732cd019a8b94c49a275661320c1b742635a3d6

6:37.82 INFO: There are no build artifacts on inbound for these changesets (they are probably too old)

Flags: needinfo?(peter.magyari)

(In reply to Edgar Chen [:edgar] from comment #5)

Might be related to Bug 1343446 or Bug 1342865.

Masayuki, do you have any idea if this is something related to Bug 1343446 or Bug 1342865?

Flags: needinfo?(masayuki)

Thanks, it must be a regression of bug 1342865.

Assignee: nobody → masayuki
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: needinfo?(masayuki)
Priority: -- → P3
Regressed by: 1342865
Has Regression Range: --- → yes

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3

Resetting assignee which I don't work on in this several months.

Assignee: masayuki → nobody
Status: ASSIGNED → NEW
Whiteboard: [platform-rel-Wikipedia]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: