Skip to content

fix: send River favicon to parent shell via postMessage#131

Open
sanity wants to merge 1 commit intomainfrom
fix/favicon-shell-message
Open

fix: send River favicon to parent shell via postMessage#131
sanity wants to merge 1 commit intomainfrom
fix/favicon-shell-message

Conversation

@sanity
Copy link
Contributor

@sanity sanity commented Mar 5, 2026

Problem

When River runs inside the Freenet gateway's sandboxed iframe, the <link rel="icon"> set by Dioxus only applies within the iframe — it doesn't propagate to the parent shell page's tab icon. The shell page shows a generic Freenet favicon instead of the River logo.

Solution

On app initialization, query the <link rel="icon"> element's resolved href and send it to the parent shell via the existing __freenet_shell__ postMessage bridge (type: 'favicon'). The shell's bridge JS already handles this message type and updates the parent document's favicon.

Testing

[AI-assisted - Claude]

The Freenet gateway shell page uses a generic Freenet favicon by default.
River's <link rel="icon"> inside the sandboxed iframe doesn't propagate
to the parent shell. Send the favicon URL to the parent via the
__freenet_shell__ postMessage bridge on initialization so the browser
tab shows the River logo.

Companion to freenet/freenet-core#3428.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant