Use window.top and window.top.document#294
Use window.top and window.top.document#294eoghanmurray wants to merge 6 commits intorrweb-io:masterfrom
Conversation
|
Great work eoghanmurray! |
136f8df to
c42cfb5
Compare
|
@Juice10 I hadn't envisioned that usecase and haven't tested that. I just came across this since reading your comment: Do you have a chance to test out what would happen with multiple iframes in the same document? |
191259c to
4a602b9
Compare
@eoghanmurray I'm not sure to be honest.
Yes I'd be happy to, anything specific you'd like me to do? Just do a recording with this branch? Any specific pages you'd like me to try out? One thing that might make electron based recording a little trickier is that every iframe/browser-window has its own |
|
The electron (https://www.electronjs.org/ ?) application of rrweb is definitely not on my radar, I was only thinking of the web; so I guess a run through it's paces would be great to make sure this change doesn't break things there. |
46b2d38 to
5b3207c
Compare
|
Should this be a configuration option for it to be accepted? |
5b3207c to
65a975d
Compare
d6d9aee to
6b6bc4d
Compare
…rt recording there
… reversal of events vs. expected output here)
…tally listen on the wrong document in a multiple frame context
6b6bc4d to
0c57091
Compare
…rent environments (I can't see how the `positions` attribute is normalised away in record.test.ts if indeed it is)
|
Any update regarding this PR? How can we move things forward? I wonder if it would be better to add |
I think both will be good, but I think it should default to the highest window it can find |
This pull request is to break out of simple same-domain <iframe>s, i.e. when rrweb.js is loaded from within the iframe.
This is the case for GoDaddy.
I'm not sure whether this is generally a good idea for all of rrweb's users, so maybe it needs further consideration before being accepted?