Closed Bug 518462 Opened 16 years ago Closed 14 years ago

can't drag a new url in bookmarks toolbar

Categories

(Firefox :: Bookmarks & History, defect)

3.5 Branch
x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
status1.9.1 --- wontfix

People

(Reporter: laurens.v, Unassigned)

Details

(Whiteboard: [CLOSEME 2011-2-15])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) if i drag a url in the bookmark toolbar is does not work, in the recent versions of firefox it did work. (if i right-klik on the bookmark toolbar and ad a new url it does work, but that's not fast, unlike firefox :) ) Reproducible: Always Steps to Reproduce: 1.left klik on url 2.left klik on url and hold 3.drag url to the bookmark toolbar 4.rejection mark appears... Expected Results: the bookmark toolbar does not place the url in it's toolbar the url would be able to be dropt in the bookmark toolbar
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.4pre) Gecko/20090923 Shiretoko/3.5.4pre This works fine for me. Have you tried: - Firefox's safe-mode to exclude extension/theme problems - a new profile - a reinstallation in a new empty folder http://support.mozilla.com/en-US/kb/Safe+Mode http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile
Component: General → Bookmarks & History
QA Contact: general → bookmarks
Version: unspecified → 3.5 Branch
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-15]
not going to fix this in 3.5, should work pretty fine in 4.0.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.