Closed Bug 353179 Opened 19 years ago Closed 17 years ago

dragging bookmarks from 1.5 -> 2.0 creates empty bookmarks

Categories

(Firefox :: Bookmarks & History, defect)

x86
Linux
defect
Not set
minor

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jacob, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1) Gecko/20060918 BonEcho/2.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1) Gecko/20060918 BonEcho/2.0 I have multiple profiles set up so that i can run versions of 1.0, 1.5, 2.0, and 3.0 simultaneously. If i try to drag a bookmark from the toolbar in 1.5 and drop it on 2.0's toolbar, i get an empty bookmark (no name or location). Reproducible: Always Steps to Reproduce: 1. open firefox 1.5 and 2.0 using different profiles 2. add a bookmark to 1.5's toolbar 3. drag it over to 2.0's toolbar (and hold down ctrl when dropping) Actual Results: a label-less bookmark with a blank file icon is created which does nothing if clicked on. Expected Results: At least the url would be copied over, optimally the label and other properties as well.
Summary: dargging bookmarks from 1.5 -> 2.0 creates empty bookmarks → dragging bookmarks from 1.5 -> 2.0 creates empty bookmarks
WFM with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060917 BonEcho/2.0
I could reproduce this on Windows using 1.5.0.7 and both 2.0 beta 2 and the latest nightly.
sorry, hitting enter submitted. anyway, just to be clear, i am running both 1.5 and 2.0 at the *same* time. which version of 1.5 were you testing against?
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.