3 ms·

Sounds like something similar to the PawClaws project: https://chrome.google.com/webstore/detail/pawclaws/figeaallbafpdefmmkfipkgdgpknmhfl?hl=en https://chrome

by msla 7y ago

Sounds like something similar to the PawClaws project: https://chrome.google.com/webstore/detail/pawclaws/figeaallbafpdefmmkfipkgdgpknmhfl?hl=en https://chrome.google.com/webstore/detail/pawclaws/figeaallb... https://github.com/TobiasKundig/PawClaws https://github.com/TobiasKundig/PawClaws https://github.com/PawClaws/chromePawExt https://github.com/PawClaws/chromePawExt I wonder though: How do you deal with asynchronous sites which may take a variable amount of time for elements to load? Do you synchronize with Angular or try to detect elements or is it just the old stopwatch-and-pray technique?

yaseer 7y ago
Very, very good question. The long-story short is that I don't think there's an algorithm that can determine the completion of page-load with certainty for complex JS SPAs. We fingerprint elements, check if the page is changing along the critical path and wait if it is, and look at network traffic. We can't say with certainty, but we can form a good guess - the accuracy of that guess is always improving. This is something I think would benefit from open-source collaboration, if we went down that route.