User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:22.214.171.124pre) Gecko/20090903 SeaMonkey/2.0b2 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:126.96.36.199pre) Gecko/20090903 SeaMonkey/2.0b2 In SeaMonkey 1.x, it was possible to put a given bookmark into several folders by clicking on the bookmark in Bookmark Manager, copying and pasting into another folder. In Seamonkey 2.x this does not work; one has to separately copy the name and location of the site, create a new bookmark, paste name and location and move the newly-created copy to the new folder. Reproducible: Always Steps to Reproduce: 1.In Bookmark Manager, click on a bookmark. 2.Copy it (Command-C). 3.Open another folder in Bookmark Manager. 4.Click in the folder and past (Command-V). Actual Results: Nothing Expected Results: The bookmark should now appear in the new folder below the place which had been clicked and where pasting had been attempted. Mac G4 (PPC), OS X 10.4.11
Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:188.8.131.52pre) Gecko/20091007 SeaMonkey/2.0pre I confirm this bug in Win XP SP3 Steps to Reproduce: It is same as in steps 1 to 4 5) restart Bookmark Manager 6) Bookmark isn't in new place
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac OS X → All
Hardware: PowerPC → All
Version: unspecified → Trunk
Created attachment 405240 [details] [diff] [review] Proposed patch I accidentally removed this vital bit of code which ensures that we really copy (otherwise we assume a move, which is bad if we didn't cut in the first place!)
Assignee: nobody → neil
Status: NEW → ASSIGNED
Attachment #405240 - Flags: review?(iann_bugzilla)
Pushed changeset 3a35f91ecc51 to comm-central. If you're looking for changeset 12c1bb7cfeb1, that was really bug 521112.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Working - VERIFIED
Status: RESOLVED → VERIFIED
I note that this has now been marked as 'Working', but it does not work in the new stable SeaMonkey 2.0 on a Mac G4 (PPC), OS X 10.4.11.
You need to log in before you can comment on or make changes to this bug.