scrollOffset not respected
See original GitHub issueHi Erik,
See the following Sandbox: https://codesandbox.io/s/react-laag-menu-viewport-margin-x40cc
When opening the menu, it has no margin relative to the viewport:
Even though scrollOffset: 12
. Any idea what is the problem here?
Issue Analytics
- State:
- Created 4 years ago
- Comments:21 (21 by maintainers)
Top Results From Across the Web
c# - OnDrawItem does not respect horizontal scroll position ...
It seems like the horizontal scroll offset is lost somewhere on the way and the area OnPaint() has been called to fill in...
Read more >scroll-padding - CSS-Tricks
scroll-padding is part of the CSS Scroll Snap Module. Scroll snapping refers to “locking” the position of the viewport to specific elements ...
Read more >Mouse scrolls editor when Cursor Surrounding Lines is set
Successfully merging a pull request may close this issue. Respect default behaviour of cursorSurroundingLines cvaldev/Vim. 2 participants. @ ...
Read more >ASP.NET Core Data Grid Component Scrolling Overview
By default, the Grid does not display scrollbars when scrolling is enabled. ... variable which will hold the scroll positions. var scrollOffset =...
Read more >Scroll-linked Animations - W3C
If the sampling of such an animation causes a change to a scroll offset, the animation will not be re-sampled to reflect the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll close this one, will reopen if I run into the issue again but assume it’s fixed. Thanks for the help so far.
Thanks for noticing! Well, the option has been renamed:
scrollOffset
>containerOffset
. I will fix this in the release notes right away!