Closed
Bug 426254
Opened 17 years ago
Closed 12 years ago
Keyboard focus lost when mouse is used on Google apps
Categories
(Toolkit :: Find Toolbar, defect)
Toolkit
Find Toolbar
Tracking
()
RESOLVED
INVALID
People
(Reporter: mattmay, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4
Clicking on a link in Google Reader causes keypresses to be consumed by the find panel. I have verified this with on FF3 on XP, Vista and OS X Tiger and Leopard.
This worked properly in Firefox 2, and on every other browser I've tested. This behavior makes keyboard interaction extremely difficult.
Reproducible: Always
Steps to Reproduce:
1. Go to http://reader.google.com. Keyboard shortcuts are j and k to move up and down between items in a feed; n and p to move keyboard focus between items without opening them; o to open and close; and capital J, K, and O to do the same in the tree of feeds.
2. Verify that these keystrokes work as indicated.
3. Open an item and click on its title to open the item in a new window.
4. Return to the Reader window, and press j or k. (See results.)
5. Click inside the document on a non-link, and press j or k to see that keyboard interaction is restored.
Actual Results:
Outcome: Find panel opens in OS X, and if "Search for text when I start typing" is enabled on Windows. (workaround: you can shift-tab until keyboard focus is on a frame or on the chrome, but until you do this, any keystroke will be consumed by the find panel.)
Expected Results:
Firefox should continue passing keystrokes into the document.
See Firefox 2 behavior.
| Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
Comment 1•12 years ago
|
||
"Google Reader has been discontinued." https://www.google.com/reader/about/
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•