Skip to content

Preview: pop out a rendered HTML page to the system browser #2143

Closed

Description

@jacktrnr

Important

Problem — A researcher who wants the dashboard on a second monitor has no way to open the previewed page in a browser: the bridge's open-external path passes only https URLs.
Approach — A pop-out control on rendered HTML posts a dedicated bridge message carrying the file's absolute path; the extension opens it with the system handler only if it is an existing local .html/.htm file, and names the reason otherwise (remote window, missing file, wrong type).
Scope — in: control, message, extension handler · out: serving the page over HTTP.

Acceptance Criteria

  • The control appears only for rendered HTML and posts the message with an absolute path.
  • The extension opens an existing local .html/.htm file in the system browser.
  • A relative path, a missing file, a non-HTML extension, or a remote editor window is refused with a named warning and nothing opens.

Testing Decisions

Extend the chat bridge tests for the new message kind (accept + each refusal).

Key Decisions

A new message kind rather than widening open-external: the https-only rule stays intact, and the type restriction stops the bridge from launching arbitrary local files.

Source

Part of #2140. Blocked by #2141.

Metadata

Metadata

Assignees

Labels

afkImplementable without human interactionarea:webviewenhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions