Translate OnlyOffice error dialogs into actionable host-UI errors #154

New issue

Open

opened 2026-04-26 08:19:04 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-26 08:19:04 +00:00

Member

Acceptance

A small DOM watcher (or postMessage listener if OnlyOffice exposes one) inside the iframe wrapper detects the error dialog appearing.
Replace it with a host-rendered banner that:
- Names the file and the doc type.
- Shows a short, plain-English diagnosis ("the editor service couldn't reach the file — your admin should check that hero_office_server is running").
- Offers a Retry button that closes the iframe and re-creates the editor session.
Underlying OnlyOffice error stays available behind a "Show technical details" toggle for support diagnostics.

When the editor fails (host mismatch in cache URL, encoding issue, JWT mismatch, ...) OnlyOffice shows raw "Download failed" / "Unknown error" / "Error" dialogs that mean nothing to a user. The host application has the context to translate these. ## Acceptance - A small DOM watcher (or postMessage listener if OnlyOffice exposes one) inside the iframe wrapper detects the error dialog appearing. - Replace it with a host-rendered banner that: - Names the file and the doc type. - Shows a short, plain-English diagnosis ("the editor service couldn't reach the file — your admin should check that hero_office_server is running"). - Offers a Retry button that closes the iframe and re-creates the editor session. - Underlying OnlyOffice error stays available behind a "Show technical details" toggle for support diagnostics.