Since Chrome and Microsoft Edge version 153, the WebOffice Administration (SynAdmin) and the WebOffice HTML client show a red warning in many tables and lists:

"This site uses XSLT; that functionality is being removed from this browser very soon..."

As a result, rows may be shifted and tables may appear only partially or not fully rendered. Firefox is currently not affected by this behavior.

Why this happens

The WebOffice Administration and HTML client render tables, lists, and trees using XSLT. Google and Microsoft are gradually removing XSLT support from Chromium-based browsers:

• Chrome/Edge version 153 shows the warning.
• Chrome/Edge version 158 disables XSLT in the stable channel.
• Firefox also plans to remove XSLT support in the future.

Affected versions

WebOffice 10.8, 10.9, 10.9 R2, 10.9 R3, 10.9 R4, and 10.9 R5.

Workaround

WebOffice uses an official XSLT polyfill instead of the browser's native XSLT engine. This restores correct rendering of tables in Chrome, Edge, and Firefox. Internet Explorer is not affected.

Download: WebOffice_Bug408325_XSLT-Fix_10.8-10.9R5.zip

How to apply the fix

<WebOffice> refers to the WebOffice application directory in Tomcat, for example:

C:\Tomcat\webapps\WebOffice

1. Make a backup of the file <WebOffice>\client\JSX\js\JSX30.js in a location outside the webapps directory.
2. Extract the ZIP file.
3. Copy the client folder from the ZIP file into the WebOffice directory and confirm replacement of existing files.
4. A Tomcat restart is not required.
5. Clear the browser cache or reload the page using Ctrl + F5.

Check: Open the WebOffice Administration in Chrome, Edge, or Firefox and go to the Projects and License tabs. The red warning should no longer appear and rows should display completely.

Rollback

Restore the backed-up JSX30.js file and remove the client\JSX\js\xslt-polyfill folder.

Notes

• If your application_config.xml contains a custom Content Security Policy and the script-src directive does not include 'unsafe-eval' or 'wasm-unsafe-eval', add 'wasm-unsafe-eval'.
• On first access, the browser downloads approximately 1.5 MB of additional data. After that, the file is reused from the browser cache.

Temporary workaround without file replacement

If you cannot apply the file change immediately, you can temporarily:

• use Firefox, or
• enable the browser policy XSLTEnabled.

Set the policy in the registry under:

• HKLM\SOFTWARE\Policies\Microsoft\Edge
• or HKLM\SOFTWARE\Policies\Google\Chrome

Value: XSLTEnabled, type: REG_DWORD, value: 1.

This workaround keeps XSLT available only until Chrome/Edge version 176 (around August 2027). For long-term stability, we recommend applying the file fix or upgrading to a version that includes the fix.