User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4 Enter key can be used to open emails in GMail, if keyboard shortcut is enabled. However, Firefox 3 Beta seems to have problems with this feature. Pressing Enter key sometimes affects nothing. No email is opened, even thought the page is refreshed. Reproducible: Always Steps to Reproduce: 1. Login to gmail 2. Enable keyboard shortcut 3. Try using Enter key to open emails Actual Results: No email is opened after pressing Enter key Expected Results: Email being pointed must be opened after pressing Enter key

Confirmed as still broken in 3.0b5, at least on OS X. It's the only keyboard navigation feature of GMail that's not working; unfortunately, it's probably the worst one to be broken. I have to reach for the mouse every time I want to read a message. The actual result of pressing the return key, btw, is that the GMail "cursor" graphic moves to the top message on the page.

Confirmed on OSX for B5. I don't know about other OS ... I agree that this is pretty debilitating for one of the most popular web apps out there.

It's not an OS X thing; same behavior confirmed on Linux (Ubuntu Gutsy) and Windows (Vista Home Premium). There's another issue in that the keyboard focus is not set properly when first loading the GMail page, so it's necessary to click in the message list before even trying to confirm this bug. Will go look for an open bug on that issue...

As soon as I posted that last comment and went back to GMail, the shortcut started working. It's consistently working for me now on the different OSes... maybe Google added a workaround to their javascript?

This is WFM. (In reply to comment #3) > There's another issue in that the keyboard focus is not set properly when first > loading the GMail page, so it's necessary to click in the message list before > even trying to confirm this bug. Will go look for an open bug on that issue... If that bug isn't filed, please make sure that it is. Do we know why it's happening? Is it a regression?