Closed Bug 192011 Opened 22 years ago Closed 22 years ago

[Mach-O] Multiple Bookmarks changes don't survive Mozilla application quit/restart

Categories

(SeaMonkey :: Bookmarks & History, defect)

Product:
SeaMonkey
Component:
Bookmarks & History
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
mozilla1.3final

People

(Reporter: rgould, Assigned: janv)

References

Details

(Keywords: dataloss, regression, Whiteboard: [adt1] fixed1.3)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030205 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030205 mac mach-o builds fail to save changes to bookmarks (file) when moving bookmark entries (folders and sites) via bookmark manager. it appears to save the first move, but loses the rest. but it adds and deletes multiple entries without a problem (which is better than it used to be). this has been an issue since before december 2002. this is an issue with new and old profiles. Reproducible: Always Steps to Reproduce: 1.open bookmark manager 2.move multiple entries 3.quit application 4.launch application 5.notice only one of the entries has moved Actual Results: only one entry has moved. Expected Results: saved the positions of all changes made by bookmark manager.
*** Bug 192083 has been marked as a duplicate of this bug. ***
*** Bug 192334 has been marked as a duplicate of this bug. ***
Severity: normal → major
Summary: nightly mach-o builds are unable to save multiple move changes in the bookmarks file → [Mach-O] Multiple Bookmarks changes don't survive Mozilla application quit/restart
Confirming on 2003020403.... although it didn't save any change if i made more then one.
Status: UNCONFIRMED → NEW
Ever confirmed: true
It looks like being fixed in 2003020903 build. I'll test todays build to see if the fix will be permanent.
The behavior from bug 192083 looks like being fixed in build 2003020903 and 2003021003. However, the bug referenced here (bug 192011) is not. I did the steps to reproduce the bug and there is still a critical problem.
I think that the root cause of both this one and bug 192124 is the same - see my comment bug 192124#c4
Flags: blocking1.3?
Blocks: 192124
Flags: blocking1.3? → blocking1.3+
nominating. also blocking 1.3
Keywords: nsbeta1
*** Bug 193473 has been marked as a duplicate of this bug. ***
*** Bug 193500 has been marked as a duplicate of this bug. ***
*** Bug 193520 has been marked as a duplicate of this bug. ***
*** Bug 193180 has been marked as a duplicate of this bug. ***
Blocks: profile-corrupt
*** Bug 193718 has been marked as a duplicate of this bug. ***
*** Bug 193089 has been marked as a duplicate of this bug. ***
keyword love
Keywords: dataloss, regression
-> Jan
Assignee: ben → varga
Nav triage team: nsbeta1+/adt1
Keywords: nsbeta1 → nsbeta1+
Whiteboard: [adt1]
Target Milestone: --- → mozilla1.3final
I think we can safely mark this as a dupe of 192124
Altough bug 192124 and 192011 speak about the same bookmark issues, they differ in some tricky ways. However, they share the same root. See comment http://bugzilla.mozilla.org/show_bug.cgi?id=192011#6
fixed by fix for bug 192124
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Whiteboard: [adt1] → [adt1] fixed1.3
*** Bug 195446 has been marked as a duplicate of this bug. ***
Verified in the 2003-04-22-08 Macho trunk.
Status: RESOLVED → VERIFIED
Blocks: bookmark-loss
No longer blocks: profile-corrupt
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.