Failed to execute 'postMessage' on 'DOMWindow'
See original GitHub issueEmbedding video to the page causes this error in the console:
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://www.youtube.com') does not match the recipient window's origin (*host name*)
“Angular YouTube Embed” has the same problem.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:17
- Comments:5
Top Results From Across the Web
Failed to execute 'postMessage' on 'DOMWindow': https://www ...
I believe this is an issue with the target origin being https . I suspect it is because your iFrame url is using...
Read more >Failed to execute 'postMessage' on 'DOMWindow ... - GitHub
Hi David, I face an issue when using your scripts in sharepoint sites. Failed to execute 'postMessage' on 'DOMWindow': The target origin (https://....
Read more >Failed to execute 'postMessage' on 'DOMWindow'
Youtube player widget, out of nowhere, started to show errors in browser console. www-widgetapi.js:758 Failed to execute 'postMessage' on 'DOMWindow': The ...
Read more >JavaScript : Failed to execute 'postMessage' on 'DOMWindow'
JavaScript : Failed to execute ' postMessage' on 'DOMWindow ': https://www.youtube.com !== http://localhost:9000 [ Gift : Animated Search ...
Read more >Failed to execute 'postMessage' on 'DOMWindow': The target ...
Currently, I'm facing an issue. Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://companyName--c.visualforce.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
i yust had the same issue and at least in my local enviroment setting :player-vars=“{origin:‘http://mydomain.local’}” seems to solve the issue