Closed Bug 308067 Opened 19 years ago Closed 19 years ago

Dragging multiple items from History or Bookmarks to Finder only creates one webloc

Categories

(Camino Graveyard :: Drag & Drop, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 182785
Camino1.5

People

(Reporter: alqahira, Unassigned)

Details

Follow-on to bug 278929 and bug 230340.

When you drag two or more entries from History to the Finder, Camino only
creates a webloc for the topmost item (even if it wasn't the first item
selected), not for all of the dragged items.

Camino 2005091104 (v1.0a1)
Actually, the Finder is creating the webloc; the reason for this bug, AFAIK, is
that only one URL can be stored on a pasteboard at once.
Hrm, I see this is the case with Bookmarks, too, but I'm fairly certain I used
to be able to drag multiple bookmarks to the Finder and get multiple weblocs....
Target Milestone: --- → Camino1.1
Version: 1.8 Branch → Trunk
Summary: Dragging multiple items from History to Finder only creates one webloc → Dragging multiple items from History or Bookmarks to Finder only creates one webloc
(In reply to comment #1)
> Actually, the Finder is creating the webloc; the reason for this bug, AFAIK, is
> that only one URL can be stored on a pasteboard at once.

FWIW, this works from Safari; it even shows a badge indicating the number of bookmarks/history items I'm dragging.  It'll even drag an entire bookmarks folder and create a folder with that name filled with all the weblocs (when you drag the "folder" for an entire day of history, it just creates the weblocs loose, though).

So presumably this is not unsurmountable.
Assignee: mikepinkerton → nobody
QA Contact: drag.drop
Can this be duped to bug 182785, which appears to be exactly the same thing? (Or vice-versa.)

cl
Wow, I feel dumb (or this was broken then, fixed at some point, and broke again)....

*** This bug has been marked as a duplicate of 182785 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.