Closed
Bug 1497759
Opened 7 years ago
Closed 5 years ago
Gmail does not recognize (asterisk, *) for threadlist selection
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P2)
Core
DOM: UI Events & Focus Handling
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: t.matsuu, Unassigned)
References
Details
Threadlist selection (asterisk, *) still does not work.
Step to Reproduce:
1. In any threadlist, select threads by using threadlist selection shortcuts (* + a, * + u, etc.).
Expected: Select all (* + a) or unread (* + u) conversations.
Actual: Nothing happens.
Additional info:
Other shortcuts works good for me. So this issue is different from bug 1471848.
At the least on 2018-07-02, these shortcuts don't work.
I'm using japanes 106/109 keyboard.
Does it depend on keyboard layout?
Comment 1•7 years ago
|
||
Masayuki might know the answer.
Did this work in the past?
Flags: needinfo?(t.matsuu)
Flags: needinfo?(masayuki)
Priority: -- → P2
Comment 2•7 years ago
|
||
I don't understand how to use the shortcut key. I tried to do it on Chrome, but nothing happens. Could you let me know detail of the STR? (I do NOT use Gmail in daily use...)
Flags: needinfo?(masayuki)
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to Masayuki Nakano [:masayuki] (JST, +0900) from comment #2)
Instruction for enabling keyboard shortcut (and list of shortcuts) is shown in the URL below.
https://support.google.com/mail/answer/6594
Flags: needinfo?(t.matsuu)
Comment 4•7 years ago
|
||
I didn't understand which UI should be shown, which element should have focus at pressing the shortcut key.
But I succeeded to reproduce it now.
Even if enabling dom.keyboardevent.keypress.set_keycode_and_charcode_to_same_value, I cannot use it. Perhaps, we're banned by UA string check or something?
Anyway, I cannot read their minimized JS...
Assignee | ||
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
Reporter | ||
Comment 5•5 years ago
|
||
Now threadlist selection works!
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•