Skip to content

Open in browser must support custom URI #40

@asfalots

Description

@asfalots

I am trying to use the "Open in Browser" action to trigger local application commands using custom URI schemes (such as obsidian:// or slack://).

Currently, the action forcibly prepends https:// if the URL does not explicitly start with http or https. This breaks custom protocols, rendering the button useless for local app control.

Many productivity tools (Obsidian, Slack, Zoom, Proton apps) rely on custom URIs to control application behavior externally. Supporting this allows Stream Deck users to map complex local workflows (like opening a specific note or joining a meeting) to a single button.

Steps to Reproduce

  • Create a button with the "Open in Browser" action.
  • Set the URL to a custom URI, for example: obsidian://open?vault=ttrpg.
  • Press the button on the Stream Deck.

Expected Behavior

The system should respect the provided protocol and open the URI exactly as entered (e.g., launching the Obsidian app).

Actual Behavior

The application modifies the URL before executing it.
Input: obsidian://open?vault=ttrpg

Result: The browser/OS receives a malformed URL obsidian//open?vault=ttrpg , causing the link to fail or open a search engine result instead of the app.

Root Cause

I investigated the source code and located the issue. The logic assumes that if a URL is not HTTP/S, it must be a web link missing the protocol.

if not url.startswith("http://") and not url.startswith("https://"):
url = "https://" + url

The validation logic should check if a protocol scheme is already present before prepending https://. A simple check for the existence of :// might be sufficient,

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions