![]() I'm not sure, though, why the load event would be triggered at interactive and not complete. My understanding is that TamperMonkey's document-idle listens to the event DOMContentLoaded, which would explain why the script is injected long before the page is done loading. Listening for the load event appears to work the same way. What I am seeing, instead, is that the script gets triggered about at the same time as readyState reaches interactive. So the load event should be firing shortly after readyState turns from interactive to complete. The state indicates that the load event is about to fire. The document and all sub-resources have finished loading. The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets and frames are still loading.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |