Henric Persson
Henric Persson
Can you describe more specifically what's not working? Is it that the waypoints aren't firing at all? Or perhaps firing at the wrong time?
If you add the `debug` prop to the waypoints, the console log might contain some information that can help you resolve this.
This shouldn't be because of flexbox or css grid. In the debug output, I would check that the scrollable ancestor is set to the right elements (the `.column` divs).
I wonder if the styles are applied asynchronously some way? Do things change if you inject styles earlier somehow?
By the way, thanks for being so persistent here. I appreciate you trying to pin this down!
Thanks for sharing the workaround @rosskevin. I agree that it's a little brittle, and it makes me wonder if it would be easier to just attach a separate scroll handler...
Ah, that makes things a little trickier. If you have ideas for how we could improve waypoint to cover this use-case, let me know. :)
Thanks for diving in to this @MatthewHerbst! We already have a workaround for composite children (the `innerRef` prop). Instead of attaching the ref to the `React.Fragment` wrapper, how about we...
The main reason we don’t wrap things in a div is that we don’t want to interfere with styling too much. Let’s say you have a flexbox container with multiple...
Are all mobile browsers failing or is it a specific one? We don’t look at the user-agent string in react-waypoint, but you might have a difference in layout/styling depending on...