Skip to content

fix postMessage targetOrigin #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
severo merged 1 commit into from
Jul 31, 2025
Merged

fix postMessage targetOrigin #37

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions src/components/App/App.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,11 +87,15 @@ export default function App() {
*
* Note that the iframe has no access to the parent window's location, so
* it might already by in sync, we just don't know.
*
* Also, trying to access the parent window's origin will throw an error:
* DOMException: Permission denied to access property "origin" on cross-origin object
* so we cannot test it before sending the message to a specific targetOrigin.
*
* We thus send the message to any origin ('*') and hope that the parent window
* will handle it correctly.
*/
const huggingfaceOrigin = 'https://huggingface.co'
if (window.parent.origin === huggingfaceOrigin) {
window.parent.postMessage({ queryString: window.location.search }, huggingfaceOrigin)
}
window.parent.postMessage({ queryString: window.location.search }, '*')

return <ConfigProvider value={config}>
<Page source={source} navigation={{ row, col }} />
Expand Down