feat(tangle-cloud): honor iframe requestConnect — open the parent wallet modal#3251
Merged
Merged
Conversation
The Header computed breadcrumbs but never rendered them. Show the trail
("Blueprints / Trading") in the nav left slot by default, with the leading
"Cloud" dropped and section roots (Blueprints/Operators/Instances) linking
back. Pages can still override via useTopNavSlot; the blueprint detail now
injects a matching "Blueprints / <name>" trail alongside its Create/Details
actions instead of a "← Catalog" link.
The sandbox Button variant left dark, italic text on its purple fill (unreadable). Render the Create action as an explicit styled link: white text on a solid accent fill, non-italic, sized to match the Details button.
…xt module The context module intentionally exports its Provider alongside its hooks; the react-refresh/only-export-components rule doesn't apply. Disable it at the two hook exports so the project lints clean.
…let modal An embedded blueprint (sandboxed, no wallet of its own) can now ask the dapp to connect a wallet via tangle.app.requestConnect. The bridge: - answers immediately if a wallet is already connected; - otherwise opens the parent's wallet-connect modal (new app-level WalletConnectModalContext mounting one EvmWalletModal) and resolves the request when an account appears — or rejects it if the user dismisses the modal, so the iframe never hangs. Gated read-tier in policy (allowReadAccount). Protocol + validator mirror the SDK's tangle.app.requestConnect / connectResult. This is what lets BOTH the thin-iframe apps (useTangleWallet().connect()) and full-iframe wagmi apps (eth_requestAccounts via the parent-bridge connector) connect from inside the iframe without breaking the sandbox model.
tangletools
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lets an embedded blueprint initiate a wallet connection without breaking the sandbox model — the missing piece behind "connect inside the iframe doesn't do anything."
A sandboxed iframe can't reach a wallet extension, so it delegates to the parent via the new
tangle.app.requestConnect(SDK side merged in blueprint-ui #22, published 0.5.2). The bridge:WalletConnectModalContextmounting oneEvmWalletModal) and resolves the request when an account appears — or rejects it if the user dismisses the modal, so the iframe never hangs on its timeout.Gated read-tier in policy (
allowReadAccount). Protocol + validator mirror the SDK.This is what makes both tiers connect from inside the iframe:
useTangleWallet().connect();eth_requestAccountson the parent-bridge connector now drives this.Test plan
tsc --noEmitclean; protocol + policy specs green (16); full pre-push (lint/test/build) passed