Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add scrollableAncestor to debug output.
See original GitHub issueI came across this weird behavior where if when the entry point of my application is the page where I have Waypoints it works fine, but, if the entry point is a different page that leads to a page where the Waypoints are, it doesn’t.
What fixed the issue was scrollableAncestor={window}, but it took me some time to figure out that because there is no log output for scrollableAncestor.
Would be great to have this info as part of the debug output.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6
Top Results From Across the Web
How to universally enable scrolling on website that disabled ...
In a browser like Chrome etc.: Inspect the code (for e.g. in Chrome press ctrl + shift + c );; Set overflow: visible...
Read more >GitHub - civiccc/react-waypoint
A React component to execute a function whenever you scroll to an element. ... Use this prop to get debug information in the...
Read more >ScrollController class - widgets library - Flutter - Dart API docs
A label that is used in the toString output. Intended to aid with identifying scroll controller instances in debug output.
Read more >837007 - Implicit Root Scroller can prevent scrolling ... - Monorail
Go to testcase -> http://output.jsbin.com/gedurer/11 2. Try scrolling horizontally, no scrolling happens. 3. Open inspector and toggle ...
Read more >Guide to scroll anchoring - CSS: Cascading Style Sheets | MDN
What if I need to debug it? ... If any of the triggers happen on the anchor node, or an ancestor of it,...
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 Free
Top 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
Yep, that’s the idea. https://github.com/brigade/react-waypoint/commit/d1d3ff9551d8b409e0b2a0a7588ca0f4098fc5f4
Ah okay, makes sense. Perhaps the intention behind the duplicate check is so that in prod it wouldn’t even make the call to
debugLog(since that LoC would be stripped by Uglify), but I’m not sure. Perhaps @lencioni or @trotzig can shed more light there.