Open Bug 1177654 Opened 5 years ago Updated 1 year ago
Copy & paste (or drag & drop) Bookmarks folder will fail between 2 instances of browser (aka profiles)
This problem happens Bookmarks menu/toolbar as well as Library. Steps to reproduce: 1. Start Firefox[A] 2. Start Firefox[B] with -no-remote -P different profile 3. Copy a folder on browser[A] 4. Paste on browser[B] Actual Results: Bookmarks item in the folder would not be copied. The folder is empty. Expected Results: Bookmarks item in the folder should also be copied.
[Tracking Requested - why for this release]: Recent regression since Nightly41.0a1
Pushlog: https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=f28313729236&tochange=1acb10da2d7e REGRESSED BY: f79a8bc7b3c2 Marco Bonardo — Bug 1095411 - PlacesUtils.wrapNode is using synchronous getKeywordForBookmark. r=ttaubert
Summary: Bookmarks folder of copy & paste will fail between 2 instance of browser → Copy & paste Bookmarks folder will fail between 2 instance of browser
it's a minor problem affecting a rare use-case, it's not worth tracking.
I really hope this bug is fixable, thanks.
the question is whether it is planned sometime in the future to fix the bug, because it's a rare use-case.
So there are no plans to fix this "minor problem"?
Not tracking this minor regression, per comment 3.
Based on previous comments and some offline discussion I'm going to mark this fix-optional for 50/51/52.
Cool, thanks. Hope someone picks it up.
Damn. But understood.
Summary: Copy & paste Bookmarks folder will fail between 2 instance of browser → Copy & paste (or drag & drop) Bookmarks folder will fail between 2 instance of browser
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Summary: Copy & paste (or drag & drop) Bookmarks folder will fail between 2 instance of browser → Copy & paste (or drag & drop) Bookmarks folder will fail between 2 instances of browser (aka profiles)
You need to log in before you can comment on or make changes to this bug.