Closed
Bug 627582
Opened 14 years ago
Closed 7 years ago
Copying "Mobile Bookmarks" folder creates a copy named "mobile"
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: rnewman, Assigned: standard8)
References
Details
(Whiteboard: [fixed by bug 1432614 and bug 1442597])
Sync creates a Mobile Bookmarks folder in the top level:
// Use the (one) mobile root if it already exists
let anno = "mobile/bookmarksRoot";
let root = Svc.Annos.getItemsWithAnnotation(anno, {});
if (root.length != 0)
return root[0];
// Create the special mobile folder to store mobile bookmarks
let mobile = Svc.Bookmark.createFolder(Svc.Bookmark.placesRoot, "mobile", -1);
Utils.anno(mobile, anno, 1);
When copied (!) by dragging it into a different folder in Show All Bookmarks, the copied folder is named "mobile", rather than picking up the localized name for the folder.
The expected behavior would be either:
* Forbid copying this folder; or
* Carry its localized name into the copy.
This does not occur when dragging Bookmarks Toolbar or Unsorted Bookmarks.
sdwilsh's summary was "don't do that!" (re copying mobile), so I thought I'd file :)
Satisfactory resolution would also be a different invocation of createFolder that causes the correct behavior.
Tested in 2011-01-17 build of Minefield.
Updated•14 years ago
|
blocking1.9.1: --- → ?
blocking1.9.2: --- → ?
blocking2.0: --- → ?
tracking-firefox5:
--- → ?
tracking-firefox6:
--- → ?
Comment hidden (off-topic) |
Comment hidden (obsolete) |
Assignee | ||
Comment 3•7 years ago
|
||
Linking to bug 1432614, as I'm either going to need to solve this there or ensure it isn't a problem for the other folders.
Depends on: 1432614
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → standard8
Assignee | ||
Comment 4•7 years ago
|
||
With bug 1432614 landing, and now bug 1442597 as a minor bug fix on its way to landing, this is now fixed!
Status: NEW → RESOLVED
Closed: 7 years ago
Depends on: 1442597
Resolution: --- → FIXED
Whiteboard: [fixed by bug 1432614 and bug 1442597]
You need to log in
before you can comment on or make changes to this bug.
Description
•