-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
fix: droppable-get-dimension withScroll #966
fix: droppable-get-dimension withScroll #966
Conversation
@alexreardon kindly pls take a look at the pull request |
Away this week. Will look next week
…On Thu, 29 Nov 2018 at 9:02 pm, woohling ***@***.***> wrote:
@alexreardon <https://github.com/alexreardon> kindly pls take a look at
the pull request
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#966 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACFN7bVEmifeJivo-8B-J-jOZ2eUaBl5ks5uz7CYgaJpZM4Y2taj>
.
|
@@ -117,7 +117,7 @@ export default ({ | |||
|
|||
return { | |||
client: frameClient, | |||
page: withScroll(frameClient), |
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.
withScroll
will apply the page scroll
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.
You are right that your change is a bit stricter in that it does not read the page scroll directly, but just supplies it..
Thoughts?
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.
I would prefer the more strict method, it may cause potential bug which I encountered.
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.
I also like that this approach does not touch the DOM again and just uses the value that has been passed in
We're forking your amazing repo and need to add some features based on our product logic, and then I found a potential bug, which I spent a lot of time debuging.
The default container supporting horizontal scroll is the window, which would not trigger any bugs currently. But I think it would be stricter to code it this way. Pls take a look and see if I'm doing this correctly.