User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3 When attempting to drag and drop a bookmark folder from the sidebar (tree view) into the current selected (working) folder, the current folder view is switched to the folder selected in the main right view on the mouse down event instead of simply being selected for drag and drop. This prevents you from dragging it into the previously selected folder. Reproducible: Always Steps to Reproduce: 1. Select a folder you want to work in from the sidebar (treeview) 2. Select a new folder from the sidebar you wish to place into the current working folder without releasing it. 3. Watch the view change from the working folder to the selected folder. Actual Results: Working view changes from current folder to selected folder on mouse down. Expected Results: While holding the mouse button down the selected item should behave like it's going to be moved instead of switching to that selected directory. Switching to that folder should be done on release. At the moment, it appears in order to move anything into folders requires the user to actually cut and paste.
Component: Bookmarks → Places
QA Contact: bookmarks → places
I can repeat the problem with the beta3 build and the current nightly. I was able to move bookmarks into folders using the main work area space but this would be a major annoyance for users who use drag and drop using the sidebar alone. Just to clarify, I could only repeat this problem in the Bookmark Library, using the bookmarks sidebar while browsing pages, drag and drop with folders works fine. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008022504 Minefield/3.0b4pre Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9b4pre) Gecko/2008022504 Minefield/3.0b4pre
I confirm the bug, but it's not an enhancement rather than a major severity?
So, what you are saying is that if you drag from the Library left pane the selection goes to the dragged item, and the right pane contents are replaced with its contents. At that point, if you want to drag into a specific position, you can't because the left pane does not have the "spring-load" behaviour (change the selection to that folder after a timeout). So to move a folder from the left pane to a specific position into another folder in the left pane you have to copy paste or to drag into the folder and then move by hand. Confirming as an enh request to add spring-load to the left pane. I cannot reproduce any problem in the browser sidebar since containers opens after a dragover timeout, so if your intent was different try to explain it better.
Severity: major → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Summary: Cannot drag and drop folders from sidebar to selected folder without view getting stolen → Add spring-load behaviour to the Library left pane containers
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h". In Thunderbird 3.0b, you do that as follows: Tools | Message Filters Make sure the correct account is selected. Click "New" Conditions: Body contains places-to-b-and-h Change the action to "Delete Message". Select "Manually Run" from the dropdown at the top. Click OK. Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter. Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.