Yajbir-Malik/DocumentServer-v-9.2.0
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed view of the lists

Browse Source
This commit is contained in:
Denis Spitsyn
2025-02-04 15:50:05 +00:00
parent 0166a08acc
commit c1c3fc4379
1 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
CHANGELOG.md
View File

@@ -96,13 +96,13 @@
* the file version was updated when opening the editor; * the file version was updated when opening the editor;
* the connection was lost while working, and after restoring it, it was found * the connection was lost while working, and after restoring it, it was found
that the file version had changed (if there are no unsaved changes in the document). that the file version had changed (if there are no unsaved changes in the document).
For the new scheme to work, the following have been added: * For the new scheme to work, the following have been added:
* the `onRequestRefreshFile` event, which should be processed by the integrator; * the `onRequestRefreshFile` event, which should be processed by the integrator;
* the `refreshFile` method, to which it is necessary to transfer the data * the `refreshFile` method, to which it is necessary to transfer the data
recommended for opening the document (according to [documentation](https://api.onlyoffice.com/docs/docs-api/additional-api/signature/browser/#opening-file)) recommended for opening the document (according to [documentation](https://api.onlyoffice.com/docs/docs-api/additional-api/signature/browser/#opening-file));
In case of using Wopi, the file version will be updated without the need for * in case of using Wopi, the file version will be updated without the need for
changes on the part of the integrator. changes on the part of the integrator;
If the integrator has not implemented support for the new scheme, the work * if the integrator has not implemented support for the new scheme, the work
will be carried out as before — via the `onOutdatedVersion` event will be carried out as before — via the `onOutdatedVersion` event
* Added [Service Worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) * Added [Service Worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API)
to control caching of statics on the editors page to control caching of statics on the editors page
@@ -133,14 +133,20 @@ If the integrator has not implemented support for the new scheme, the work
* Updated the `customization.submitForm` configuration parameter, which is * Updated the `customization.submitForm` configuration parameter, which is
responsible for settings of the button for submitting completed forms. responsible for settings of the button for submitting completed forms.
The configuration now looks like this: The configuration now looks like this:
`submitForm`: `submitForm`:
* `visible`: `true/false` — controls the display of the button (`true`
`visible`: `true/false` — controls the display of the button (`true`
by default) by default)
* `resultMessage`: `'text'` / `''` / `null` / `undefined` — specifies
`resultMessage`: `'text'` / `''` / `null` / `undefined` — specifies
the message displayed after the form is submitted: the message displayed after the form is submitted:
* `''` (empty string) — the message is not displayed
* `null` / `undefined` — the default text is displayed `''` (empty string) — the message is not displayed
* `'text'` — the custom message is displayed
`null` / `undefined` — the default text is displayed
`'text'` — the custom message is displayed
* Preserved backward compatibility with previous versions where * Preserved backward compatibility with previous versions where
the `submitForm` parameter could take the `true`/`false` values to control the `submitForm` parameter could take the `true`/`false` values to control
the button visibility the button visibility