nextcloud / nextcloud/text

Non-http[s] links in Deck can't be opened

Open
#6,844 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: links
Dominant language
JavaScript
Stars
659
Forks
133
Avg merge
1d 20h
Merged PRs (30d)
110

Description

Note was previously logged in nextcloud/deck, but a comment suggested it should be here.

Describe the bug
Links in the description of Deck Cards that do not start http / https cannot be opened.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new Card
  2. In the Description, add three links:
  3. Name: Google; URL: www.google.com/maps
  4. Name: Joplin Example; URL: joplin://x-callback-url/openNote?id=abc
  5. Name: File Example; URL: file:///C:/Users/user.name/Folder

Expected behavior
Clicking the links in the cards should follow this pattern:

  1. Click link -> Opens preview box, showing preview (if available), link, Copy/Edit/Remove actions; clicking the preview or link opens the link per browser configuration.

Observed behavior
Clicking links which do not start (I assume) http[s]:// opens preview box, showing NO preview, link, Copy/Edit/Remove actions; nothing in the box can be clicked to open the link.

Workaround
Clicking the link, clicking the Copy Link button and pasting that URL into a new tab/window works as expected, but is a multi-step process.

Screenshots
Image
Image

Client details:

  • OS: Windows 10
  • Same behaviour on Firefox 133.0.3 and Edge Version 131.0.2903.112 (Official build) (64-bit)
  • Device: Desktop
    Note:
  • Appears to function as expected on Deck Mobile app (Android), although the File type link causes a full-on crash of the App. Anyone want me to log that?

Operating system:
Web server:
Database:
PHP version:
Nextcloud version: (see Nextcloud admin page)
Where did you install Nextcloud from:

Docker / official Nextcloud AIO Version: "Nextcloud Hub 9 (30.0.4)"
Deck Version 1.14.2

Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.

No errors have been found.

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

No source file or test is named in the issue. Start by reproducing the behavior in a Deck card description with the listed www, joplin, and file URLs, then trace the link preview interaction in the relevant frontend code. Done means the preview or link opens non-http[s] URLs according to the browser configuration without requiring copy and paste.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.