"All changes saved" message misleads user into thinking the document was saved

[LucianCheve]

Is your feature request related to a problem? Please describe or add steps to reproduce your use case.

• When editing (for example a .docx file) using the OnlyOffice connector, as soon as you start to make changes, the message "All changes saved" appears at the bottom of the screen informing you that whatever change you made was saved. This is misleading, as the document won't be saved unless you press either "Save & Continue", or "Save & View".

• This makes the user falsely believe that his edits were saved, when in reality, the save only happens if they press one of the above-mentioned buttons.

Describe the solution you'd like

• Either remove the message, or inform the user somehow (when / if they press "Cancel") that their changes were not saved

Additional context

• Even if the OnlyOffice server can be configured to autosave, there should be a check which disables the message if the autosave feature is turned off on the server.

[petrenkonikita112263]

Note this how the test OO server is set and works, and for personal OO server (local/remote) every user can enable the auto-save.

[trrenty]

Unfortunately, in order to be able to modify the layout of the onlyoffice editor we would need the "developer" edition of the api which does not have an open source license and requires MONEY. https://api.onlyoffice.com/docs/docs-api/more-information/faq/customizing/

Maybe the cryptpad fork has some development on it? https://github.com/cryptpad/onlyoffice-editor The repo mentions that its only a wrapper around it, but whats the purpose behind it?

I also considered injecting some JS or CSS into the generated iframe, but, since its content comes from another domain (the server where the OO instance resides), the browser does not allow it for security considerations.

Another possibility was to disable the auto-saving mechanism of the onlyoffice editor and control it from XWiki. However, the JS api does not provide the functionality of triggering the save command. Nor can we simulate the CTRL+S shortcut, since we need access to the content of the iframe.

Investigating all this I figured out that we have quite and unorthodox integration with onlyoffice. Normally, the configuration to the editor accepts a "callbackURL" that is supposed to point to the implementations of some document manager and storage classes. These services would receive data whenever some command/action takes place in the client editor, such as saving. https://api.onlyoffice.com/docs/docs-api/get-started/how-it-works/
There is a sdk we can use https://api.onlyoffice.com/docs/docs-api/samples/language-specific-examples/java-integration-sdk/ . Implementing this would allow us to use all the capabilities of the OnlyOffice editor and integrate it much better in xwiki - we would not need to have two concepts of saving (saving in the editor and saving in xwiki) because they would be the same thing.

[Tragen]

That sounds good but you need to consider how you update the article.
Now, you can "save" 10x in OnlyOffice but it's only saved once when you leave OO so the version counter goes up only once.
If every save in OO would result in a new version in xwiki, it would be strange in my eyes.