docs: add Global Accounts Playground page (interactive wallet demo) #581
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| --- | ||
| title: "Playground" | ||
| description: "Create a Grid Global Account and watch the API calls fire in real time" | ||
| icon: "/images/icons/phone.svg" | ||
| "og:image": "/images/og/og-global-accounts.webp" | ||
| --- | ||
|
|
||
| import { WalletDemoEmbed } from '/snippets/global-accounts/wallet-demo-embed.mdx'; | ||
|
|
||
| <div id="wallet-demo-container"></div> | ||
|
|
||
| <WalletDemoEmbed /> |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
| export const WalletDemoEmbed = () => { | ||
| React.useEffect(() => { | ||
| const isLocal = ['localhost', '127.0.0.1'].includes(window.location.hostname); | ||
| const base = isLocal ? 'http://localhost:4000' : 'https://grid-wallet-demo.vercel.app'; | ||
| const isDark = () => document.documentElement.classList.contains('dark'); | ||
|
|
||
| let host = document.getElementById('wallet-demo-host'); | ||
| if (!host) { | ||
| host = document.createElement('div'); | ||
| host.id = 'wallet-demo-host'; | ||
| host.style.cssText = 'position:fixed;z-index:1;overflow:hidden;'; | ||
| const iframe = document.createElement('iframe'); | ||
| iframe.id = 'wallet-demo-iframe'; | ||
| iframe.src = base + '/?embed=true&theme=' + (isDark() ? 'dark' : 'light'); | ||
| iframe.title = 'Grid Global Accounts — live demo'; | ||
| iframe.setAttribute('allow', 'publickey-credentials-create *; publickey-credentials-get *; clipboard-write'); | ||
| iframe.style.cssText = 'width:100%;height:100%;border:0;display:block;'; | ||
|
Comment on lines
+10
to
+17
Contributor
There was a problem hiding this comment.
The iframe embeds an external Vercel app ( Prompt To Fix With AIThis is a comment left during a code review.
Path: mintlify/snippets/global-accounts/wallet-demo-embed.mdx
Line: 10-17
Comment:
**No `sandbox` attribute on a third-party iframe**
The iframe embeds an external Vercel app (`grid-wallet-demo.vercel.app`) with no `sandbox` restrictions, giving it full access to `window.opener`, top-level navigation, form submission to any target, and more. Adding `sandbox="allow-scripts allow-same-origin allow-forms allow-popups"` (plus `allow-popups-to-escape-sandbox` if the app opens OAuth windows) would limit the blast radius if the hosted demo is ever compromised or replaced. Passkey `allow` directives work independently of sandbox and can be left as-is.
How can I resolve this? If you propose a fix, please make it concise. |
||
| host.appendChild(iframe); | ||
| document.body.appendChild(host); | ||
| } | ||
| if (window.__wdHideTimer) { clearTimeout(window.__wdHideTimer); window.__wdHideTimer = null; } | ||
| host.style.display = 'block'; | ||
|
|
||
| let raf = 0; | ||
| let last = { left: -1, top: -1, width: -1, height: -1 }; | ||
| const sync = () => { | ||
| const el = document.getElementById('wallet-demo-container'); | ||
| if (el && host) { | ||
| const r = el.getBoundingClientRect(); | ||
| if (r.left !== last.left || r.top !== last.top || r.width !== last.width || r.height !== last.height) { | ||
| host.style.left = r.left + 'px'; | ||
| host.style.top = r.top + 'px'; | ||
| host.style.width = r.width + 'px'; | ||
| host.style.height = r.height + 'px'; | ||
| last = { left: r.left, top: r.top, width: r.width, height: r.height }; | ||
| } | ||
| } | ||
| raf = requestAnimationFrame(sync); | ||
| }; | ||
|
Comment on lines
+25
to
+39
Contributor
There was a problem hiding this comment.
The Prompt To Fix With AIThis is a comment left during a code review.
Path: mintlify/snippets/global-accounts/wallet-demo-embed.mdx
Line: 25-39
Comment:
**Unbounded `requestAnimationFrame` loop runs at ~60 fps while demo is visible**
The `sync` function schedules itself unconditionally with `requestAnimationFrame` on every frame, creating a loop that runs continuously at ~60 fps the entire time the demo page is open. While the change-guard (`r.left !== last.left || …`) avoids style mutations when nothing moves, the RAF callback itself still fires and reads `getBoundingClientRect()` (which forces layout) every frame. On a static layout this is a steady tax on the main thread. Consider using a `ResizeObserver` plus a `scroll` event listener instead, which fire only on actual geometry changes.
How can I resolve this? If you propose a fix, please make it concise. |
||
| raf = requestAnimationFrame(sync); | ||
|
|
||
| let ignoreNextMutation = false; | ||
| const sendTheme = () => { | ||
| const t = isDark() ? 'dark' : 'light'; | ||
| const iframe = document.getElementById('wallet-demo-iframe'); | ||
| if (iframe && iframe.contentWindow) { | ||
| iframe.contentWindow.postMessage({ type: 'theme-sync', theme: t }, '*'); | ||
| } | ||
| }; | ||
|
|
||
| const handleMessage = (e) => { | ||
| if (e.data && e.data.type === 'theme-request') { | ||
| sendTheme(); | ||
| return; | ||
| } | ||
| if (e.data && e.data.type === 'theme-sync') { | ||
| const wantsDark = e.data.theme === 'dark'; | ||
| if (isDark() !== wantsDark) { | ||
| ignoreNextMutation = true; | ||
| document.documentElement.classList.toggle('dark'); | ||
| } | ||
| } | ||
| }; | ||
|
Comment on lines
+50
to
+63
Contributor
There was a problem hiding this comment.
The Prompt To Fix With AIThis is a comment left during a code review.
Path: mintlify/snippets/global-accounts/wallet-demo-embed.mdx
Line: 50-63
Comment:
**Unvalidated postMessage origin allows any page to manipulate theme**
The `handleMessage` handler responds to `theme-sync` and `theme-request` messages from any window without checking `e.origin`. This means any third-party site can send `{ type: 'theme-sync', theme: 'dark' }` and silently toggle the docs page's dark/light mode class on `document.documentElement`. In a cross-site scenario (e.g., a user opens a malicious link that sends a postMessage to this page), the docs UI appearance can be flipped without user consent. At minimum, validate that `e.origin` matches `base` before acting on messages.
How can I resolve this? If you propose a fix, please make it concise. |
||
| window.addEventListener('message', handleMessage); | ||
|
|
||
| const obs = new MutationObserver(() => { | ||
| if (ignoreNextMutation) { ignoreNextMutation = false; return; } | ||
| sendTheme(); | ||
| }); | ||
| obs.observe(document.documentElement, { attributes: true, attributeFilter: ['class'] }); | ||
|
|
||
| sendTheme(); | ||
| requestAnimationFrame(sendTheme); | ||
|
|
||
| return () => { | ||
| cancelAnimationFrame(raf); | ||
| window.removeEventListener('message', handleMessage); | ||
| obs.disconnect(); | ||
| window.__wdHideTimer = setTimeout(() => { | ||
| const h = document.getElementById('wallet-demo-host'); | ||
| if (h) h.style.display = 'none'; | ||
| }, 150); | ||
| }; | ||
| }, []); | ||
|
|
||
| return null; | ||
| }; | ||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
React.useEffectis called directly on theReactnamespace, butReactis never imported in this file. Mintlify's MDX pipeline uses the automatic JSX transform which does not injectReactas a named global — only JSX pragma calls are shielded. If this runs in an environment whereReactis not globally polyfilled, the component will throwReferenceError: React is not definedon mount. DestructureuseEffectexplicitly to be safe across all Mintlify versions.Prompt To Fix With AI