Closed
Bug 336624
Opened 19 years ago
Closed 19 years ago
Dragdrop link into focused search bar doesn't show the link text in search bar
Categories
(Firefox :: Search, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: martijn.martijn, Assigned: Gavin)
References
Details
(Keywords: fixed1.8.1)
To reproduce:
- Focus search bar
- Dragdrop link into search bar
Result:
"Google Search" text appears again (in my case it's Google) in the search bar
Expected result:
The url of the dragged link should appear in the search bar
I guess this could be part of Mozilla's "dragdropping something in a text input doesn't focus" syndrom.
Assignee | ||
Comment 1•19 years ago
|
||
Probably just need to reset the "empty" attribute onDrop if the dropped text is not empty, or something like that.
Assignee | ||
Comment 2•19 years ago
|
||
Actually, I can't reproduce this bug, only bug 336625. When I mousedown on a link in the content area the search bar loses focus and the grey text reappears.
Comment 3•19 years ago
|
||
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20060507 BonEcho/2.0a1 ID:2006050704
I don't understand something here. What is focusing the search bar in the first step for? It is going to be blurred in the second step anyway, when you click on a link to drag it. The "Google Search" greytext appears and we're back to bug 336625.
Reporter | ||
Comment 4•19 years ago
|
||
Doesn't work for me with current 2006-05-07 trunk build. But I think it will probably be fixed by the patch in bug 336625.
Depends on: 336625
Assignee | ||
Comment 5•19 years ago
|
||
Martijn: is this fixed now that bug 336625 is fixed on the trunk?
Reporter | ||
Comment 6•19 years ago
|
||
I'll let you know as soon as the 2006-05-12 nightly is out ;)
Reporter | ||
Comment 7•19 years ago
|
||
Yes, this one is fixed now with the 2006-05-12 build.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → gavin.sharp
Assignee | ||
Updated•19 years ago
|
Keywords: fixed1.8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•