pointer-events: none never clears after scrolling when used w/ Preact
See original GitHub issueI don’t know if this is preact specific, but 1.8.1 is broken and 1.8.0 is not, likely https://github.com/bvaughn/react-window/commit/59df8ddfc97c7f3dd1d3063eb4d905a578e90455 is the culprit.
The problem is that as soon as you scroll, pointer-events: none
gets set and never gets unset.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How do I use pointer-events to react only to scroll event?
When an element has applied pointer-events: none;. The element is never the target of any mouse events and any events are void;.
Read more >react-virtualized | Yarn - Package Manager
This supports special use-cases where deferred measuring is not desired. Added estimatedRowSize property to FlexTable and VirtualScroll to be passed through to ...
Read more >Changelog: Gameface - Coherent Labs
Enhancement, Implement optimization that caches SVGs used in elements so that the SVGs are not redrawn every frame.
Read more >Changelog | Polypane, The browser for ambitious developers
Fix Prevent vertical scrolling with height: auto panes and global zoom in horizontal layout ... New Shift to inspect elements with pointer-events: none ......
Read more >Sitemap - Sciter
Topics. Reading animated gif · There are problems with Popup samples · scroll error · Element not rendered when using CSS animation combined...
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
It is likely the same issue as this: https://github.com/developit/preact/issues/853 which is fixed in (the unreleased) Preact X
See repro: https://jsfiddle.net/deo8cahw/
null
works, is there a reason you changed it toundefined
instead ofnull
?We can stay on
1.8.0
or1.7.2
until we move to Preact X, so we’re not blocked by this. Feel free to close since it’s not really areact-window
issue unless you want/can switch back tonull
. Thanks!Cleaning up GitHub issues today. The commit you linked to was from PR #210.
Given that this change makes the validator happy, and will also work for the upcoming Preact release, I think I’m going to leave it in place. If you would like to open a PR that satisfies both Preact and the validator though- I’d be happy to tweak it! 😄
Thanks for understanding!