Closed
Bug 319559
Opened 19 years ago
Closed 19 years ago
Dragging and dropping a bookmark folder onto content opens new tabs
Categories
(Camino Graveyard :: Bookmarks, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: stuart.morgan+bugzilla, Assigned: bugzilla-graveyard)
Details
(Keywords: verified1.8)
Attachments
(1 file)
1.59 KB,
patch
|
jpellico
:
review+
|
Details | Diff | Splinter Review |
Sometime in the not to distant past, dropping a bookmark folder onto the content region started opening in new tabs, instead of replacing the current page. Was the change deliberate? It makes the behavior of dragging a folder (open in new tabs) and dragging a single bookmark (open in current tab) inconsistant, and appears to make it impossible to replace the content with a folder since the only context menu option is to open in new tabs.
Assignee | ||
Comment 1•19 years ago
|
||
This one's my fault, but I think it's because I erred on the side of caution when I fixed bug 311110. What behaviour *should* we do when dragging a folder onto an extant tab? Replace that tab and append? I think replacing current tabs other than the drag target (which is what we used to do) is a Bad Thing(tm) as it can cause data loss (or at minimum, frustration). cl
Assignee | ||
Comment 2•19 years ago
|
||
Never mind, it's not a sticky situation at all. Taking. I'll try to get this fixed ASAP. Should be a simple matter of looking at drags ending in a content area in addition to tabs. Smokey's filing a new bug on the fact that cmd-drag doesn't force append. cl
Assignee: mikepinkerton → bugzilla
Assignee | ||
Comment 4•19 years ago
|
||
Oops. At least the fix was easy. :) cl
Attachment #205368 -
Flags: review?
Comment 5•19 years ago
|
||
Comment on attachment 205368 [details] [diff] [review] one-line fix to check for overContentArea too Works as advertised
Attachment #205368 -
Flags: review? → review+
Comment 6•19 years ago
|
||
Checked in.
Comment 7•18 years ago
|
||
v on branch and trunk.
Status: RESOLVED → VERIFIED
Keywords: fixed1.8 → verified1.8
You need to log in
before you can comment on or make changes to this bug.
Description
•