Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • May 14 16:20
    eoghanmurray opened #558
  • May 13 04:59
    RobertM574 closed #557
  • May 13 03:44
    RobertM574 opened #557
  • May 13 02:31
    Mark-Fenng closed #556
  • May 12 12:25
    Wilson-hu reopened #544
  • May 12 06:25
    Yuyz0112 closed #524
  • May 11 22:57
    dependabot[bot] labeled #556
  • May 11 22:57
    dependabot[bot] opened #556
  • May 11 15:36
    eoghanmurray closed #555
  • May 11 15:13
    eoghanmurray opened #555
  • May 09 09:10
    Yuyz0112 closed #543
  • May 09 09:06
    Yuyz0112 closed #554
  • May 06 01:48
    yuanyiying123 opened #554
  • May 04 05:13
    Yuyz0112 closed #514
  • May 04 05:11
    Yuyz0112 closed #542
  • May 04 05:11
    Yuyz0112 closed #547
  • May 03 20:21
    JohnPhamous opened #553
  • May 02 13:56
    Yuyz0112 closed #550
  • Apr 29 16:36
    adhip94 closed #551
  • Apr 29 15:33
    ucjonathan closed #541
Daniël van de Giessen
Just commented https://github.com/rrweb-io/rrweb/issues/6#issuecomment-452118538, turned out to be a longer comment than I expected. It's a rough idea I had, curious to hear whether others think that would be valuable to have.
rrweb-io/rrweb#14 there is also some discussion about checkpoints in the recording side
The current timer interface makes all the things combining together, and an abstract clock you mentioned is good for solve some of the problem, especially for live streaming.
But the refactoring of the timer and the replay renderer worth a separate issue/pr, and the checkpoint part will focus on the event store:)
After the coding last night, I’m trying to figure out the impact of checkpoints in the recording side. It is useful to build some features like ‘store the last 10min records before an error exception’.
But it will reset the mirror map. Firstly I need to test this will not cause racing problems since we have many async events. Secondly also need to check it will not break the future plan of searching/filtering events.

Found a bug about shadow-DOM

Is there any other web component standard like this?

Eoghan Murray
Hi @Yuyz0112 working on rrweb-io/rrweb#221 today
just wondering are there any tslint type tools that you use for code formatting?
@eoghanmurray I use prettier for code formatting
Eoghan Murray
ok cool, I'll try to get that running on my code before I submit! I'm pretty new to typescript so let me know if there's anything you want me to fix up in e.g. rrweb-io/rrweb#223
Eoghan Murray
i.e. I wrote it to satisfy npm run typings after having started it from the definition at https://dom.spec.whatwg.org/#interface-mutationrecord
Eoghan Murray
@Yuyz0112 the #223 is currently broken, am working on a fix...
however I believe the 'should record dynamic CSS changes' test has been broken since at least
(going back further than that is giving me more general testing errors)
Eoghan Murray
ok believe #223 now doesn't introduce any new broken tests.
Eoghan Murray
feel free to ignore the note about master failing on 'should record dynamic CSS changes' ... looks like that's particular to my statcounter repository

@Yuyz0112 would it be possible to turn on Service Hooks for Travis so that the test status of pull requests is visible?
e.g. see explanation here https://stackoverflow.com/a/19810474/6691
this would enable either a green tick, or a red 'x' to appear beside the commit id in the pull request
@Yuyz0112 Hello. I got trouble implement two (or more) replays on one page. If there is only one replay it works fine. But as soon as we add a new replay to the page, the current one stop working. Any advice? Thank you.
I saw that putting the record replay in a web worker is in the roadmap. I'd like to implement it, has anyone started doing things about it?
Shakil Ahmed