record same origin <iframes> (and maybe other frames?)
See original GitHub issueI wish to record a website which has an embedded iframe, for which the
document.getElementsByTagName('iframe')[0].contentDocument.body
is accessible from the containing page (where the recorder is active).
I’m going to attempt a patch to get this included in the recording, but let me know if there are any thoughts, or situations where this would not be desirable?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Can FullStory capture content that is presented in iframes?
Yes, FullStory can work seamlessly with most iframes! Depending on your scenario, capturing iframe content may require some additional configuration.
Read more >The ultimate guide to iframes
Not a fan of iframes? This post provides an overview of the tag's best features, shows you how to use them, and how...
Read more >Same-origin policy - Web security | MDN
The same-origin policy is a critical security mechanism that restricts how a document or script loaded by one origin can interact with a ......
Read more >How to embed iframes by bypassing X-Frame-Options and ...
SAMEORIGIN : Browser will render page inside iframe only if page domain is same as domain of parent page. . Frame-ancestors directive in...
Read more >Scroll an iframe that contains a page from a different domain
You could always fake it. Maybe you could have your place your iframe in a container div (css: overflow: hidden; height: /* some...
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
This pull request: https://github.com/rrweb-io/rrweb/pull/294 is probably related; it was intended for when the rrweb code was loaded within a ‘sandboxed’ iframe, to ‘bust out’ of the iframe into the real top-level page. This type of code loading is sometimes the only way of adding 3rd party HTML/Javascript in hosted content management systems.
If we were doing that, then it would make sense to have a master/singleton instance of rrweb at the highest window, which then launches all the nested instances which report back to it.
https://github.com/rrweb-io/rrweb/pull/481