You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.
It usually takes a long time for the DOM ready event to fire. During this time, many parts of a webpage are inactive as they wait for Javascript to kick in and initialize them. This delay is significant and makes a rich web application become available slower. Creates a bad user experience, doesn’t adhere to any design pattern and is, really, not needed…
The text was updated successfully, but these errors were encountered:
@PaulKinlan i am sorry, i must have not noticed your original reply.
The practice to be analyzed revolves very specifically around the fact that you don't have to wait for the DOM Ready event to start initializing your JS Application. And a more in-depth look at how important order and position of the script tags is in your document.
And how all these techniques and patterns fit with todays modern libraries and tools
Would you be interested in a more in depth article about not using the DOM Ready Event to start a rich js app?
The text was updated successfully, but these errors were encountered: