nextcloud / nextcloud/richdocuments
Safari infinite loading when opening tagged Office documents
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Environment
- Nextcloud 33.0.5
- richdocuments 10.1.3
- Safari on macOS Tahoe 26.5.1
- MacBook Pro M2 Max
- Firefox works correctly
- Reproduced on three independent installations:
- Manual Nextcloud installation on Ubuntu LXC (Proxmox)
- Nextcloud AIO installation #1
- Nextcloud AIO installation #2
Steps to reproduce
- Create or upload a DOCX or XLSX file.
- Open the file in Safari via Nextcloud Office.
- The document opens normally.
- Add a file tag (keyword/tag) to the file.
- Close the document.
- Reopen the same document in Safari.
Expected result
The document opens normally.
Actual result
Safari shows an endless loading screen and the document never opens.
Additional observations
- Removing the tag immediately makes the document open again in Safari.
- Firefox opens the same tagged document without any issue.
- PDF files and JPG files with tags work correctly.
- The issue only affects Office documents (DOCX and XLSX tested).
- The issue started after upgrading from Nextcloud 32.x to Nextcloud 33.x.
- The same behavior occurs on three independent Nextcloud installations.
- The problem is fully reproducible.
Safari Console Error
InvalidCharacterError: Invalid qualified name: '@canAssign'
Additional console messages related to the loading process were observed, but this JavaScript error appears consistently when the issue occurs.
Summary
Office documents (DOCX/XLSX) that have one or more file tags assigned cannot be opened in Safari and remain stuck on an endless loading screen.
The same files open correctly:
- in Firefox
- after removing the file tag(s)
This suggests a Safari-specific frontend issue related to tagged Office documents in Nextcloud 33 / richdocuments 10.1.3.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce the tagged DOCX/XLSX reopening steps in Safari and inspect the Safari console for the recurring InvalidCharacterError: Invalid qualified name: '@canAssign'; compare with Firefox and untagged files. Done means tagged Office documents open normally in Safari without endless loading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100