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

Fix markdown

Browse Source
This commit is contained in:
Denis Spitsyn
2025-02-04 13:48:23 +00:00
parent 69ee5f1efa
commit bc4ebf696d
1 changed files with 9 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
CHANGELOG.md
View File

@@ -1,7 +1,5 @@
# Change log # Change log
# Change log
## 8.3.0 ## 8.3.0
### New features ### New features
@@ -95,12 +93,12 @@
* Added the ability to update the editor when the file version changes without * Added the ability to update the editor when the file version changes without
the need to reboot. The following scenarios are possible: the need to reboot. The following scenarios are possible:
- 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.
@@ -136,13 +134,13 @@ If the integrator has not implemented support for the new scheme, the work
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 * `''` (empty string) — the message is not displayed
- `null` / `undefined` — the default text is displayed * `null` / `undefined` — the default text is displayed
- `'text'` — the custom message 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