I found a related discussion that may provide some context:
Related Issue: ONLYOFFICE Workspace Community does not display files in Chrome 144+ due to XSLT removal
Context
Chrome/Edge 144 introduces several breaking changes, including:
- XSLT-related changes - Chrome is progressively Removing XSLT for a more secure browser | Web Platform | Chrome for Developers from the browser
- External XML Entity Loading - Chrome 144 stops synchronously fetching external XML entities and DTDs in non-XSLT documents (per Chrome 144 | Release notes | Chrome for Developers)
While the linked Workspace issue specifically mentions XSLT removal causing UI rendering failures, my issue appears to be in the Document Server’s fonts.js (font engine), which may be affected by similar browser-level changes in how JavaScript/WebAssembly modules are executed.
Observations
- The error occurs specifically in /sdkjs/common/libfont/engine/fonts.js at Line 35:215
- isDocumentLoadComplete: false indicates the document failed during the loading phase
- Multiple users with different memory configurations are affected
- The issue only appears after updating to Edge 144 (Chromium 144 based)
Questions for ONLYOFFICE Team
- Are there any known compatibility issues between Document Server 8.1.x and Chromium 144?
- Has the font engine (fonts.js) been tested against Chrome/Edge 144?
- Would upgrading to Document Server 8.2.x or 9.x resolve this browser compatibility issue?
- Is there a workaround (browser flags, server configuration) while waiting for an official fix?