rrwebStopRecording = rrwebRecord({
emit(event) {
chrome.runtime.sendMessage({ event, type: 'event' }, () => {
});
},
recordLog: true,
packFn: rrwebPack,
sampling: {
// do not record mouse movement
mousemove: 250,
// do not record mouse interaction
mouseInteraction: 250,
// set the interval of scrolling event
scroll: 250, // do not emit twice in 150ms
},
}); this.player = new rrwebPlayer({
target: this.$refs.playerTarget,
props: {
events: events,
},
unpackFn: rrwebUnpack,
});
Ref There is a way to add events to the player.
const replayer = new rrweb.Replayer(events)
for (const newEvent of newEvents) {
replayer.addEvent(newEvent)
}for future ref.
Ref There is a way to add events to the player.
const replayer = new rrweb.Replayer(events) for (const newEvent of newEvents) { replayer.addEvent(newEvent) }for future ref.
How can I implemet this on a rrwebPlayer instance?
const data = [{ events: <?php echo $json; ?> }];
function player(data){
const events = data.reduce((prev, cur) => prev.concat(cur.events), []);
new rrwebPlayer({
target: document.body, // customizable root element
props: {
events
},
});
}
player(data);
:wave: Hey all, I wanted to ask a couple things:
I saw mentions about a "pro plan" to support same- and cross-origin iFrame recording; what is the "pro plan" and is it available today? In general, what is the current state of iFrame recording?
I saw the warning on the npm page about v1 data structure changes; any idea how the player might handle backwards compatibility?
- same-origin iframe support has been implemented and merged into the master branch. Supporting shadow-dom will be done these days(DOM mutation observer in shadow-dom is already merged), the cross-origin iframe is still pending. pro-plan is a personal consulting plan provided by me and you can send an email to me if you are interested.
- all the recorded events will have backward compatibility in v1.0.
@/all
Hi all, I'm very happy to share an experimental product build by rrweb's core team on top of rrweb:
https://storyteller.webzard.io/?utm_source=rrweb&utm_medium=gitter
storyteller is a no-code interactive tutorial builder, you can see demos(also made by the storyteller itself!) on the website. if you want to get early access, please leave your email and we are going to contact you ASAP
rrweb.record({
emit(event, isCheckout) {
events.push(event)
},
})
Hey there,
According to the github, the issue with angular: rrweb-io/rrweb#469 was fixed in the commit rrweb-io/rrweb@13f1a61. I've tried with angular 9, then upgraded to 10 and finally to 11. They all face the same result. Screen gets frozen. I've used the example code readme for the recording.
This was done in Feb, anyone knows if it was truly fixed? shall I reopen the ticket?
@fabienc974 if you’re using a node server try increasing the json parsing limit on server side this solved errors for me because I was trying to figure out these huge request going back to server. And for the events in SPA the first batch of event is huge due to all the CSS and HTML is sent in the first request.
Hi, Droidprogrammer, I'll try it soon and I'll give a feedback asap.
