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.
How do you plan to handle dynamically loaded HTML
See original GitHub issueUnder the Limitations section I noticed you mentioned that this library does not work for dynamically injected markup, however the library should support this at some point in the future; I was wondering if you had a plan for implementing this. It seems like using MutationObserver is a good idea, as it is widely supported (including back to IE11), and should be able to efficiently listen to DOM mutations. I’m guessing we could observe on document.body or something and listen for childList mutations, determine if a child has the .lazy class, and therefore should also be observed?
Maybe we could make mediaObserver a variable global to this module, so we could .observe future elements that our MO detects. Thoughts?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Oh nice, sounds fun! Excellent, we shall talk soon then.
And yeah, I’ve been contributing to Chromium + standards a bit. Ah I’m interested in seeing some of the writing if it’s been published yet!
This has been added in the 2.0.0 release. Closing.