Closed Bug 398041 Opened 18 years ago Closed 17 years ago

Incorrect cursor when hovering over the location bar

Categories

(Firefox :: Address Bar, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: laufdal, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7 If you click on the search bar, and it is not focused, it selects all the text in the search bar, so that you can write over the selected text. This is OK. But the incorrect behavior is that when you put the mouse cursor over the search bar (when it is not focused) it shows the IBeam cursor instead of the Arrow cursor. The IBeam cursor indicates that you can click and the input cursor is positioned exactly where you clicked, but in this case this is not what happens, because the whole text gets selected. I hope my description is clear. If you don't understand what I mean you can compare how the mouse cursor is when you put it over the search bar on the Internet Explorer. They have correct behavior. Reproducible: Always Steps to Reproduce: 1. Open firefox and put the mouse over the search bar and the cursor should be showing an arrow instead of IBeam 2. 3. Actual Results: Mouse cursor shows IBeam Expected Results: Mouse cursor should show Arrow
Summary: Mouse over on Search bar → Incorrect cursor when hovering over the search bar
In my description I meant to say the "Location bar" not the "Search bar" (meaning the location bar where you type the URL). Sorry about that.
Component: Search → Location Bar and Autocomplete
Summary: Incorrect cursor when hovering over the search bar → Incorrect cursor when hovering over the location bar
QA Contact: search → location.bar
Bulk closing all UNCONFIRMED bugs dealing with places that haven't had any bug activity in over 120 days, have no votes, and are not enhancement requests. If you are still experiencing this issue in Firefox 3.0 or later, please re-open the bug with steps to reproduce (if they were not part of the original comment).
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.