1434786 - No prompt to save changes after publish page

Status: UNCONFIRMED

(SeaMonkey :: Composer, defect)

Description

[Michael Schmitt]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/604.4.7 (KHTML, like Gecko) Version/11.0.2 Safari/604.4.7

Steps to reproduce:

1. File > Open File

2. Select a local .html file to open.

3. File > Edit Page to open the .html file in Composer.

At this point the Save button is greyed out.

4. Make some edits to the file.

   When the first change is made, the Save button becomes available. This is correct.

5. Click Publish, Publish to publish the file to the web server.

6. Click the Composer window's close button.

   


Actual results:

The composer window closed without prompting to save the changes that were made. Those edits are lost; they only exist in the published on the web server.

If the user is expecting the local copy to the be the canonical source (i.e. all changes are made to it and then published) then the next time the document is edited there will be regression.


Expected results:

Closing the window should have displayed the "Save Page", "Save changes to xxxx before closing?" sheet, to prompt user to save the changes.
 
A related problem is if the user:
1. Edits document.
2. Publish.
3. Makes more changes.
4. Close window.

In this case, you get a prompt to PUBLISH the changes, but if you decline, it again closes the window without saving the changes to the local document.

Note 1: I *think* this is a change in behavior. I've been using SeaMonkey for years, but in December is the first time I've lost work this way.
 
Note 2: On macOS the proper behavior is documents with unsaved changes have a dot in the center of the window close button. SeaMonkey isn't doing this.

Note 3: For what it's worth, in Claris HomePage the act of publishing would always save the document first.