-
Notifications
You must be signed in to change notification settings - Fork 9
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
Better explanation of how it should work #31
Comments
I am still trying to remember why margin was picked over padding, and believe me - I’ve spend a few months playing around it (now I remember it) but so far the best (but not good) source of information for me is my younger me - https://medium.com/react-camp/how-to-fight-the-body-scroll-2b00267b37ac |
This issue has been marked as "stale" because there has been no activity for 2 months. If you have any new information or would like to continue the discussion, please feel free to do so. If this issue got buried among other tasks, maybe this message will reignite the conversation. Otherwise, this issue will be closed in 7 days. Thank you for your contributions so far. |
I got the issue with this package and I tried to figure out how it's supposed to be used properly.
To debug my issue and figure out options I created this snippet that sets different values of
padding
andmargin
to<body>
and with differentgapMode
: https://codesandbox.io/s/remove-scroll-bar-i7obpkIt seems for me like it works not very stable with
gapMode=margin
. Withpadding
mode it seems more robust, but doesn't take into account previous value.I'd be happy to help and make it handling all those cases, but I expect there are more of them. So if you can help me with more use cases I'd be able to help you coding the fix. Alternatively I'd expect some documentation of what this package expect to be set over
<body>
to keep it working.The text was updated successfully, but these errors were encountered: