3 ms·
I think it would be way better to explain in the repository: - how do you handle images? - does it handle embedded videos? - does it handle JS? to what exten
by alpb 7y ago
I think it would be way better to explain in the repository:
- how do you handle images?
- does it handle embedded videos?
- does it handle JS? to what extent?
- does it handle lazily loaded assets (i.e. images that load only when you scroll down, or JS that loads 3 seconds later after the page is loaded)
In general, how does this work? The current readme doesn't do a decent job explaining what the tool exactly is. For all I can tell, it probably just takes a screenshot of the page, encodes as base64 into the html and shows it.
- flatroze 7y agoGood points, thank you for the review. I'll work on enhancing the readme file to be more informative.
- deleted 7y ago[deleted]
- quickthrower2 7y agoIt can’t handle JS completely because we can’t predict a programs behaviour using static analysis. See Halting Problem for example.
- kuzehanka 7y agoI saw a tool that handles JS to a limited extent by capturing and replaying network requests to accommodate said JS. It records your session while you interact with a site, and is then able to replay everything it captured. This tool was able to capture three.js applications and other interactive sites quite well.
- penagwin 7y agoSure but many websites load resources and such with JS - the request might not contain the content but 3 seconds on the page with JS to let it fill in everything, etc. SPA's often (but not always) do this. Content is loaded in via React components and such...