Closed Bug 1471848 Opened 7 years ago Closed 7 years ago

Gmail: Pound (hash, #) sign to delete selected conversations no longer works since Wed Jun 27, works in Chrome

Categories

(Web Compatibility :: Site Reports, defect, P1)

x86
Windows 10

Tracking

(firefox63 affected)

RESOLVED FIXED
Tracking Status
firefox63 --- affected

People

(Reporter: MarcoZ, Unassigned)

References

Details

(Whiteboard: [sitewait][parter-rel-Google])

STR: 1. Turn on extended keyboard shortcuts in your Gmail settings. See: https://support.google.com/mail/answer/6594?hl=en 2. In any conversation list, use the arrow keys to select a thread, then press x to add it to the selection. 3. With one or more items selected, press #. Expected: This should move the items to the Trash. Actual: Nothing happens. This started on Wednesday morning GMT, late Tuesday evening PDT time. It affects Firefox 60.0.2, 61, 62beta3, and 63 nightly, so is nothing that got pushed in some code change. I suspect some ad-hoc pref change that was pushed through update channels. It works as expected in Chrome, both release and Canary. Affected types of Gmail accounts: Both Mozilla as well as personal accounts show this behavior on my two Windows machines. Other shortcuts listed above are not affected, it's the # key specifically.
curiously, I can't reproduce this with 63 nightly. I get the expected results with the STR. Marco, is this with the new Gmail interface or the current one?
(In reply to James Teh [:Jamie] from comment #1) > curiously, I can't reproduce this with 63 nightly. I get the expected > results with the STR. > > Marco, is this with the new Gmail interface or the current one? Both. No difference between them.
More information: This is not dependent on the lanuage of Firefox or Gmail. Both Firefox in English and German (the latter being my default) exhibit this, as well as Gmail set to either German (my default) or English. Reproducible on two machines 100% of the time on two accounts, one of them being Mozilla, the other my private Gmail account. Nothing in the web console pertaining to this, either.
Side thought: I'm using a customized shortcut to remove emails (*), and it stopped working as well.
Smaug, there might be a problem getting the regression window, since this bug started affecting all versions of Firefox from 60.0.2 through 63.0a1 all at once, starting, from my timezone, on Wednesday June 27th, in the morning.
Flags: needinfo?(bugs)
All shorcuts other than threadlist selection work for me.
oh, so this is not our regression, but Gmail regression. Has anyone reported this issue to Google then?
Flags: needinfo?(bugs)
Summary: Gmail: Pound sign to delete selected conversations no longer works since Wed Jun 27, works in Chrome → Gmail: Pound (#) sign to delete selected conversations no longer works since Wed Jun 27, works in Chrome
I have reported to Google for comment #5 and comment #7.
Summary: Gmail: Pound (#) sign to delete selected conversations no longer works since Wed Jun 27, works in Chrome → Gmail: Pound (hash, #) sign to delete selected conversations no longer works since Wed Jun 27, works in Chrome
Couldn't reproduce this on linux nor on windows. Using Nightly I suppose they fixed it
It's still broken for me, after a cache-clean and forced page refresh. 60.0.2 on Linux.
Still broken for me, FF61 Windows10
Still broken for me on the latest nightly (63.0a1, Build ID: 20180703100028) on Windows 10 x64.
Still broken for me as well on Windows 10, two machines, and 3 different Firefox versions, with two Gmail accounts, one personal, one G Suite.
I have the same issue. As another clue I'm using an UK keyboard. If you press ' (for quick find) and the ESC, the shortcut works (but need to do this again to reuse the shortcut). Version 62.0b5 ID build 20180702164905
This very much sounds like a change in gmail, not in Firefox.
I sent email to Google folks, hopefully they'll forward to gmail team.
Component: Keyboard: Navigation → Desktop
Product: Core → Tech Evangelism
See Also: → 1463777
Priority: -- → P1
Whiteboard: [sitewait][parter-rel-Google]
FWIW, Google reported back "We're aware of the issue and tracking this internally with bug xxxx."
Rcemoving the regression keyword as this is not a problem on our side.
Keywords: regression
Yup, me too. There is a Mozilla Support thread, and a GMail support thread about this, in case you need affected people to ask questions :) * https://productforums.google.com/forum/#!msg/gmail/YGiJ50_0y0c/D_p5XHAJDQAJ * https://support.mozilla.org/en-US/questions/1224114
New development. My previous workaround no longer works. I was pressing (on my UK keyboard) ' to bring up Quick Find, Esc to close it, then # to delete the email. As mentioned more than once above that always worked for some reason. Now pressing Esc after ' places my cursor inside the search box (same effect as pressing /), breaking the workaround. Sad :(
Firefox version 62.0 just dropped on Ubuntu - this issue is still not fixed (I'm also on a UK keyboard) I did find a work-around: in Gmail settings -> advanced, enable "Custom keyboard shortcuts". You can then re-map one of the other keys to delete - I picked 'd' but ymmv.
(In reply to simongareththorpe from comment #22) > New development. My previous workaround no longer works. I was pressing (on > my UK keyboard) ' to bring up Quick Find, Esc to close it, then # to delete > the email. As mentioned more than once above that always worked for some > reason. Now pressing Esc after ' places my cursor inside the search box > (same effect as pressing /), breaking the workaround. Sad :( Can't see how to delete this comment, but for some reason today this behaviour has ceased and I can now once again use the old 'Esc# workaround.
I am having a related issue. In addition to delete shortcut `#`, the shortcut for search `/` does not work either. Pressing `/` opens the ff's quick find bar rather than changing the focus to Gmail's find mail search field. I am on windows 10 and use a french keyboard, firefox version is Quantum 62.0.3 (64-bit)
As of 2018-10-03, the '#' shortcut has started working for me again. I'm currently using FF 62.0.3, but since the thread says this was a Gmail code problem, I assume that something has - finally - been fixed at the Google end.
Yes, I can confirm that # works for me again as well.
Sounds like this was fixed. Thanks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.