Closed
Bug 33546
Opened 24 years ago
Closed 24 years ago
Drop in wrong position with an open container
Categories
(SeaMonkey :: Bookmarks & History, defect, P3)
SeaMonkey
Bookmarks & History
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: mikepinkerton, Assigned: mozilla)
Details
- open bookmarks - open up a folder with a couple of bookmarks in it - drag a bookmark and position the mouse so that it is the lower 1/4 of the container so that the drop feedback is drawn between the container and its first child (which is indented). - drop the bookmark expected: - the bookmark should be moved to be the first child of the open parent actual: - the bookmark is moved after the open parent and is a sibling of the parent. I know the drop feedback is currently being drawn incorrectly for this (i'm fixing it now), but i'm not sure the right way to handle this code-wise. I can't exactly change the "target" node from w/in the capturer, so it seems that this needs to be accounted for in the JS. However, this really sucks for everyone that does tree d&d. Any bright ideas?
Assignee | ||
Comment 1•24 years ago
|
||
I don't like this bug. Pink, make it all better. :^)
Assignee: rjc → pinkerton
Reporter | ||
Comment 2•24 years ago
|
||
i'll look into changing the event.target on the fly. i'll email hyatt and joki.
Status: NEW → ASSIGNED
Reporter | ||
Comment 3•24 years ago
|
||
ok, hyatt says i can't change the event.target node, so this has to be acccunted for in JS. cc'ing candice because she probably has to do it too for mail trees. basically, when the event.target is a container, but the drop hint says to put it after, the JS has to check if the target is _open_. If so, this means to make it the first child of that container. If the container is closed, then put the item _after_ the container. make sense?
Assignee: pinkerton → rjc
Status: ASSIGNED → NEW
Assignee | ||
Comment 4•24 years ago
|
||
Just checked in a fix (for bookmarks).
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Does this affect status for bug 14449 ? Seems similar problems used to be placed as duplicates there..
Assignee | ||
Comment 6•24 years ago
|
||
No, this bug has no affect on the status of bug # 14449.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•