-
-
Notifications
You must be signed in to change notification settings - Fork 5
[HIG-2959] Fix: scrolling on elements being is ignored #93
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
Conversation
aptlin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
HIG-2959 rrweb scrolling conflicts with css body scrolling disabled
I think Highlight's session recording or playback might not be accounting for sites that disable body scrolling in favor of scrolling elements within the page with 100% height, using CSS that looks like this: |
|
Should this go to #94 instead? |
f143d48 to
e92e64b
Compare
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the `scrollTo` api as it doesn't have that issue.
e92e64b to
7ec25a3
Compare
update to include HIG-2959 fix as well as updating rrweb fork. see highlight/rrweb#94 and highlight/rrweb#93
## Summary update to include HIG-2959 fix as well as updating rrweb fork. see highlight/rrweb#94 and highlight/rrweb#93 ## How did you test this change? Recording and replaying my own session with the new rrweb in client and frontend. Canvas recording, obfuscation, normal record/replay look good. https://frontend-pr-3200.onrender.com/1/sessions/ZvuQEPT1Hqrsmiqgb9sMrJlOheY0?page=1&query=and%7C%7Ccustom_created_at%2Cbetween_date%2C30%20days ## Are there any deployment considerations? Bumped client version to keep track of new sessions. Using https://static.highlight.run/beta/index.js to test new client for app.highlight.run recordings. Will remove beta build after this is merged.
## Summary update to include HIG-2959 fix as well as updating rrweb fork. see highlight/rrweb#94 and highlight/rrweb#93 See #3200 Fixed by reverting rrweb-io/rrweb#962 which causes problems. Will be pointing out the observers issue there. This also cleans up some client state logic which should make sure we do not call `rrweb.addCustomEvent` which we are not recording ## How did you test this change? Before:  After:  ## Are there any deployment considerations? Bumped client version.
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the `scrollTo` api as it doesn't have that issue. Co-authored-by: Justin Halsall <[email protected]>
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the `scrollTo` api as it doesn't have that issue. Co-authored-by: Justin Halsall <[email protected]>
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the `scrollTo` api as it doesn't have that issue. Co-authored-by: Justin Halsall <[email protected]>
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the `scrollTo` api as it doesn't have that issue. Co-authored-by: Justin Halsall <[email protected]>
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the `scrollTo` api as it doesn't have that issue. Co-authored-by: Justin Halsall <[email protected]>
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the `scrollTo` api as it doesn't have that issue. Co-authored-by: Justin Halsall <[email protected]>
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the `scrollTo` api as it doesn't have that issue. Co-authored-by: Justin Halsall <[email protected]>
In certain cases when scrollLeft is being set, but the value doesn't change. Then scrollTop is also ignored, even if that value was changed. In this case we use the
scrollToapi as it doesn't have that issue.