Drop indicator should reflect depth of resulting item around folders

RESOLVED INACTIVE

Status

()

RESOLVED INACTIVE
11 years ago
3 months ago

People

(Reporter: christineyen+bugs, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
Created attachment 270042 [details]
screenshot

In the screenshot, if the user was to let go (with the drop indicator at the bottom of a folder, and the cursor below the drop indicator), the Google item would be placed outside the folder but in the following row. If the mouse cursor was above the drop indicator, the Google item would be dropped inside "New Folder." The drop indicator, though, doesn't change at all to reflect this.

Actual results: the drop indicator is always the same length/implies that the item will be dropped inside the folder

Expected results: the drop indicator should shift left to indicate a change if it will be dropped on the same level as "New Folder" and "Ask.com."
(Reporter)

Updated

11 years ago
Target Milestone: --- → Firefox 3
(Reporter)

Updated

11 years ago
Assignee: christineyen+bugs → nobody
Target Milestone: Firefox 3 → ---
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

Comment 2

3 months ago
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: 3 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.