Closed Bug 128538 Opened 23 years ago Closed 23 years ago

composer doesn't save changes

Categories

(SeaMonkey :: Composer, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: asa, Assigned: Brade)

References

Details

(Keywords: regression, smoketest)

composer doesn't save. more info coming
Keywords: smoketest
Initial save in composer works but cannot make changes to that saved document and then save the changes. Tested Windows and Linux and both fail. Will test Mac next.
Blocks: 122050
Summary: composer doesn't save → composer doesn't save changes
Since when, what checkin yesterday? We need to calibrate our drivers web-of-trust, if possible. /be
are we forgetting to pass in PERSIST_FLAGS_REPLACE_EXISTING_FILES somewhere?
Something like that. I backed out the latest rev (1.99) of editor/ui/composer/content/ComposerCommands.js and it then worked. That's the editor code that does the call to nsWebBrowserPersist. Kathy Brade checked that in yesterday. I'll get on somebody's case about it...
Assignee: syd → brade
That was for bug 125070. The changes don't match what's in the patch for that bug, so maybe that's the reason.
This needs to be fixed on the branch and the trunk, BTW.
also experienced this just now with 2002.03.01.08 comm bits on rh7.2. i just lost several hours of work!
OS: Windows 2000 → All
Hardware: PC → All
My regrets; that's what I was afraid of. I'm just now preparing to back out the code in question.
I've backed out the latest rev of ComposerCommands.js on the branch. I'll do that on the trunk as soon as tbox goes green. I've re-opened bug 125070.
Status: NEW → RESOLVED
Closed: 23 years ago
Keywords: regression
Resolution: --- → FIXED
Verified, I am able to save on Win XP using the 03-04 trunk build. If anyone is still seeing this problem, feel free to reopen it.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.