Document fails to open with Edge 144 - fonts.js changesError

Docs
1

Do you want to: Report a bug

Document Server version:8.1.1
Type of installation of the Document Server (docker, deb/rpm, exe, please point us to the installation guide that you used as well):docker
OS:
Browser version:Edge 144.0.3719.82
Additional information:
After updated browser to Edge version 144.0.3719.82, documents fail to open in OnlyOffice editor. The editor shows an error message with error code -82: “An error has occurred while opening the file.”

This issue does NOT occur with older browser versions (e.g., Edge 143.0.3650.96).

The following errors appear in the Document Server logs:

[2026-01-19T03:42:03.322] [ERROR] [localhost] [-752708132] [USER1] nodeJS - clientLog: changesError: Error: Uncaught 1802488
Script: https://[server]/8.1.1-26/sdkjs/common/libfont/engine/fonts.js
Line: 35:215
userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 Edg/144.0.0.0
platform: Win32
isLoadFullApi: true
isDocumentLoadComplete: false
performance.memory: {“totalJSHeapSize”:338855009,“usedJSHeapSize”:260684697,“jsHeapSizeLimit”:4294967296}
StackTrace: undefined

[2026-01-19T04:07:26.069] [ERROR] [localhost] [-829408898] [USER2] nodeJS - clientLog: changesError: Error: Uncaught 1016200
Script: https://[server]/8.1.1-26/sdkjs/common/libfont/engine/fonts.js
Line: 35:215
userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 Edg/144.0.0.0
platform: Win32
isLoadFullApi: true
isDocumentLoadComplete: false
performance.memory: {“totalJSHeapSize”:275090195,“usedJSHeapSize”:201634171,“jsHeapSizeLimit”:2248146944}
StackTrace: undefined

Questions

  1. Is this a known compatibility issue with Edge 144.0.3719.82?
  2. Would upgrading to a newer version (e.g., 9.x) resolve this issue?
2

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:

  1. XSLT-related changes - Chrome is progressively Removing XSLT for a more secure browser  |  Web Platform  |  Chrome for Developers from the browser
  2. 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

  1. Are there any known compatibility issues between Document Server 8.1.x and Chromium 144?
  2. Has the font engine (fonts.js) been tested against Chrome/Edge 144?
  3. Would upgrading to Document Server 8.2.x or 9.x resolve this browser compatibility issue?
  4. Is there a workaround (browser flags, server configuration) while waiting for an official fix?
3

Frustratingly, I am seeing the same thing from my clients.

They are on 44.0.3719.82 and getting this error as of yesterday.

Bizarrely, I am also on 44.0.3719.82 and not getting this error!

Completely at a loss!

4

Hello @Donglin

XSLT deprecation has nothing to do with fonts.js and it is posted in Workspace category. I can confirm that the linked topic is not the cause of the issue. Moreover, I have also updated Chrome to 144 and do not experience any issues with latest version of Document Server. I’d recommend updating and then troubleshoot the issue, in case it appears again.

@paulf, can you specify the usage of Document Server? Is it used in a ready-to-go solution like Nextcloud?

Status code -82 refers to unknown format being used, which specifically refers to the use case. Can you elaborate?

5

Hi,

Thank you for your response. I have a follow-up question:

You mentioned that Chrome 144 works fine with the latest version of Document Server. Could you also confirm whether Edge 144 works without issues?

On my end, I’ve tested both browsers:

  • Chrome 144 — Works fine ✓
  • Edge 144 — Still experiencing the issue ✗

If Edge 144 also works on your side, I will investigate further to see if there’s something specific to my environment causing the problem.

Thanks!

6

I confirm it works with Edge 144.0.3719.82 (official build). In the meantime, you can try accessing your Document Server from Incognito mode to see if something changes, cache, for instance.

1 Like
8

Running into the same issue here though the error code is different:

[2026-01-22T05:17:52.416] [ERROR] [localhost] [230052375] [oc2ik2a2d4s5_B9FA4CCE-E8C9-4DE2-96E7-ACD1FFE4B9EE12] nodeJS - clientLog: changesError: Error: Uncaught 987896
 Script: https://xxx/9.2.1-78bf3a2cbc07abae69b59c4a26b80487/sdkjs/common/libfont/engine/fonts.js
 Line: 52:442
 userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 Edg/144.0.0.0
 platform: Win32
 isLoadFullApi: true
 isDocumentLoadComplete: false
 performance.memory: {"totalJSHeapSize":102900872,"usedJSHeapSize":92514096,"jsHeapSizeLimit":4294967296}
 StackTrace:

This doesn’t happen on all computers for some reason I haven’t figured out. Chrome works, Edge fails. So probably some feature flag thing somewhere.

1 Like
10

@here, our QA team has confirmed the issue. It affects Edge browsers with enhanced security enabled in options. We are investigating this issue to find the cause and resolve it.

I will keep this topic up to date.

2 Likes
11

@here, it seems that Microsoft has released patch 144.0.3719.92 for Edge that fixes the issue. Please try updating your browser and share a feedback.

1 Like
12

It works fine now. Thanks for your help in verifying this.

1 Like