-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PostHog session recording only captures first section on the page of about 8 sections revealed on scrolled. #12690
Comments
Hello @benjackwhite, |
Hi @Forison I suspect this is an issue with the underlying recording library we are using, rrweb. If it's at all possible it would be good to try to reproduce this purely with rrweb and see if the problem still persists. And if so, we can make a request to the upstream to resolve the issue there. What do you think @benjackwhite ? |
Hello @benjackwhite and @hazzadous |
hello @benjackwhite and @hazzadous |
@Forison ah so rrweb manages to capture the scroll mutations? It's possible that the latest rrweb version includes a fix for the scrolling capture. @benjackwhite do you have any insights here? |
@hazzadous yes, it works fine, it recorded all section of the page as expected |
@hazzadous @benjackwhite Looks like they have fix for scroll rrweb-io/rrweb#1029 |
@Forison can you provide us with something to help us debug further like a link to the recording and a link to the page that doesn't seem to be recorded properly? Can I ask what version of rrweb you used to test it with where everything seemed to work correctly? |
@benjackwhite probably the latest version |
Nice find! That is likely the fix. We decided not to use the alpha version of rrweb as it has a lot of other issues that are still being ironed out but sadly until that is released it seems all the fixes are only going to be available there... Normally we like to live on the edge but here we took a more cautious approach. I'm going to investigate if we can have some way of "opting-in" to the latest versions as I feel for some cases like this the alpha version is already better than the existing one. |
Thank you @benjackwhite . For sure, I understand your concerns about alpha version. But currently we are blocked in providing the best level of support for our customers without this feature. Is there a way that you can ask rrweb team to backport this fix to older stable version of |
Hello @hazzadous and @benjackwhite |
@Forison were you able to fix this ? facing the same issue, only the main scroll is recorded, our UI is built on div scrolling so we see the user just clicking and scrolling on the first page Screen.Recording.2022-12-23.at.10.00.46.AM.mov |
@Forison @mohammadameer I suspect this isn't too high on the list of team session recordings priority list, but if you spot a new release of rrweb then shout. I think that's the most likely outcome, but @benjackwhite will have more context. |
The default version is now rrweb 2 |
Viewport Scrolling is not captured by PostHog session recording
Please describe.
We are currently having issues with PostHog session recording. The recording occurs on a SPA. The page has about 8 sections, each section becomes visible after the user clicks a button and the viewport is scrolled automatically (via react-scroll, version 1.8.2) so that the new section is at the top of the page. what happens currently now is that the application works fine but the recording only points to the first section of the page whilst the remaining sections are not recorded. Looks like the recording does not capture the automatic scrolling. On the hand events are emitted which shows clearly that the user is going through the flow, but the video can't capture the subsequent sections.
How to reproduce
There about eight sections revealed on scroll
User clicks
enter button
inside the first section to auto-scroll to the next section, session recording captures the first section.Session recording gets stack on the very first section whilst user actually goes through the flow
Environment
Additional context
Thank you for your bug report – we love squashing them!
The text was updated successfully, but these errors were encountered: