Closed
Bug 284112
Opened 20 years ago
Closed 20 years ago
[Options-Landing] Download Actions->Search bar loses focus when scrolling
Categories
(Firefox :: Settings UI, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: u88484, Assigned: bugs)
Details
(Keywords: regression)
Steps to reproduce: 1) Tools->Options->Downloads->'View and Edit Actions' 2) Point and click in the search bar (caret blinks) 3) now scroll with the scrollbar and the caret is gone (search bar loses focus)
Keywords: regression
Comment 1•20 years ago
|
||
Yup, seeing this too. If I just move the mouse over the list area and use the scrollwheel, focus stays. But if I click on the scrollbar and drag, focus is lost.
Comment 2•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050227 Firefox/1.0+ Confirming
Comment 3•20 years ago
|
||
when scrolling the list get the focus (selected or current row), it's look normal to me. i don't think this is bug.
Comment 4•20 years ago
|
||
As far as I know, the list should only be getting the focus if an item inside the list is clicked, not merely by clicking the scrollbar. Try putting your cursor in the URL bar in Mozilla, then clicking and scrolling the page with the scrollbar. Focus remains in the URL bar unless you click inside the page. It would seem this should have the same behavior.
Comment 5•20 years ago
|
||
Bookmarks Manager and about:config behave the same as download actions. A normal window behaves different, the focus stays in search/find/location as long as you only pull the slider.
Comment 6•20 years ago
|
||
Peter, agreed that this is the correct behavior for a non standard window in Mozilla... based on current operation of History, about:config, and Bookmark Manager windows. Marking INVALID.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Comment 7•18 years ago
|
||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in
before you can comment on or make changes to this bug.
Description
•