nextcloud / nextcloud/richdocuments

Opening a document in a new tab does not work reliably on Chromium-based browsers

Open
#5,937 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
453
Forks
147
Avg merge
14h 54m
Merged PRs (30d)
83

Description

Describe the bug

When trying to open multiple Collabora document types in new tabs (using middle-click or CMD+click), only sometimes Collabora opens. In the majority of cases, a buggy Files tab opens. This happens in Chrome and Vivaldi on macOS, and in Chrome on ChromeOS. We did not observe this bug in Firefox.

To Reproduce

Steps to reproduce the behavior:

  1. Open a folder with multiple Collabora-documents in Files
  2. Middle-click or CMD+click on several of the documents
  3. Several new tabs open
  4. Switch to the new tabs
  5. Notice that only in about 30% of the cases, the new tab will show Collabora with the desired document. In about 70% of the cases, the new tab will show Files, and it is additionally not possible to click on the desired document. Only reloading this tab fixes the situation and opens Collabora

Expected behavior

The expectation is that when opening multiple documents in new tabs, every new tab will open Collabora and show the desired document in 100% of the cases.

Screenshots

Screen recording that demonstrates the behavior (Chrome 150.0.7871.185):

https://cloud.101lab.it/s/QmQToXgNyapcNzj

Client details:

  • OS: we observed this on macOS and ChromeOS
  • Browser: Chrome and Vivaldi (both Chromium-based), Firefox is not affected
  • Version: Chrome 150.0.7871.185, latest Vivaldi
  • Device: desktop

Browser logs:

Browser Log when failing (new tab does not open Collabora):

Failing

Browser Log when working (new tab opens Collabora, two screenshots):

Working 1 Working 2

Server details

We observed this on the following combinations of Nextcloud and Richdocuments:

  • NC 32.0.12, RD 9.1.0
  • NC 32.0.13, RD 9.2.0
  • NC 33.0.6, RD 10.2.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in Chrome or Vivaldi on macOS or ChromeOS using the documented multi-tab steps, then compare the failing and working browser logs included in the report. The work is done when every opened tab reliably loads Collabora with the selected document, without requiring a reload, while Firefox behavior remains unaffected.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.