Recent changes to DOMContentLoaded

DOMContentLoaded modified by mmartz

mmartz — Fri, 09 Aug 2019 19:45:08 -0000

--- v2
+++ v3
@@ -1,5 +1,5 @@
 [toTop]: #content_base "Top"
-[toBottom]: #site-footer "Bottom"
+[toBottom]: #notes "Bottom"
 ## Description

 The code in a Greasemonkey user script gets invoked when the `DOMContentLoaded` event fires. It is a [DOM event](https://developer.mozilla.org/docs/Web/API/Event) implemented by Mozilla, similar to [window.onload](https://developer.mozilla.org/docs/Web/API/GlobalEventHandlers.onload). However, since it waits only for the [DOM](https://developer.mozilla.org/docs/Web/API/Document_Object_Model) to load, instead of the entire page *(including images, style sheets, and etc.)* it happens sooner. The `DOMContentLoaded` event does not fire for non-text content types such as images. 
@@ -19,3 +19,7 @@
 Using a combination of [userContent.css](http://kb.mozillazine.org/UserContent.css) and [@-moz-document()](https://developer.mozilla.org/docs/Web/CSS/@document) rules, the page can be hidden completely. The Greasemonkey script would then be crafted to undo this CSS rule, after altering it, thereby never showing the page in its pre-greased state. 

 [⬆][toTop] [⬇][toBottom]
+
+## Notes
+
+[⬆][toTop]

DOMContentLoaded modified by Martz

Martz — Sun, 10 Aug 2014 06:35:11 -0000

--- v1
+++ v2
@@ -1,39 +1,21 @@
+[toTop]: #content_base "Top"
+[toBottom]: #site-footer "Bottom"
 ## Description

-The code in a Greasemonkey user script gets invoked when the 
-    
-    DOMContentLoaded
+The code in a Greasemonkey user script gets invoked when the `DOMContentLoaded` event fires. It is a [DOM event](https://developer.mozilla.org/docs/Web/API/Event) implemented by Mozilla, similar to [window.onload](https://developer.mozilla.org/docs/Web/API/GlobalEventHandlers.onload). However, since it waits only for the [DOM](https://developer.mozilla.org/docs/Web/API/Document_Object_Model) to load, instead of the entire page *(including images, style sheets, and etc.)* it happens sooner. The `DOMContentLoaded` event does not fire for non-text content types such as images. 

-event fires. It is a [DOM event](http://developer.mozilla.org/en/DOM:event) implemented by Mozilla, similar to [window.onload](http://developer.mozilla.org/en/DOM:window.onload). However, since it waits only for the [DOM](http://developer.mozilla.org/en/DOM) to load, instead of the entire page _(including images, style sheets, and etc.)_ it happens sooner. The 
-    
-    DOMContentLoaded
-
-event does not fire for non-text content types such as images. 
-
-[Workaround](#Workaround) 
+[Workaround](#workaround) 

 ## Flicker

-Although it happens sooner than the 
-    
-    Load
+Although it happens sooner than the `Load` event *(`onload`)*, there is still a delay between when the page starts loading and when this event fires. This delay is the amount of time that it takes for the HTML content of the page itself to load. Greasemonkey injects [user script](User_script)s at `DOMContentLoaded` time. Thus, there is a period of time when the page is loading, and may be showing on screen, before Greasemonkey has injected into the page. This delay is often known as **flicker**, where the page appears to load, then changes after a *(usually)* short delay. 

-event _(
-    
-    onload
-
-)_, there is still a delay between when the page starts loading and when this event fires. This delay is the amount of time that it takes for the HTML content of the page itself to load. Greasemonkey injects [user scripts](User-Script) at 
-    
-    DOMContentLoaded
-
-time. Thus, there is a period of time when the page is loading, and may be showing on screen, before Greasemonkey has injected into the page. This delay is often known as **flicker**, where the page appears to load, then changes after a _(usually)_ short delay. 
-
-[top](#top) 
+[⬆][toTop] [⬇][toBottom]

 ## Workaround

 Generally, flicker is a problem that should be ignored. If, however, a script author decides that it must be avoided there is at least one technique. 

-Using a combination of [userContent.css](http://kb.mozillazine.org/UserContent.css) and [@-moz-document()](http://developer.mozilla.org/en/CSS:%40-moz-document) rules, the page can be hidden completely. The Greasemonkey script would then be crafted to undo this CSS rule, after altering it, thereby never showing the page in its pre-greased state. 
+Using a combination of [userContent.css](http://kb.mozillazine.org/UserContent.css) and [@-moz-document()](https://developer.mozilla.org/docs/Web/CSS/@document) rules, the page can be hidden completely. The Greasemonkey script would then be crafted to undo this CSS rule, after altering it, thereby never showing the page in its pre-greased state. 

-[top](#top) 
+[⬆][toTop] [⬇][toBottom]

DOMContentLoaded modified by Martz

Martz — Fri, 27 Jun 2014 23:42:47 -0000

Description

The code in a Greasemonkey user script gets invoked when the

DOMContentLoaded

event fires. It is a DOM event implemented by Mozilla, similar to window.onload. However, since it waits only for the DOM to load, instead of the entire page (including images, style sheets, and etc.) it happens sooner. The

DOMContentLoaded

event does not fire for non-text content types such as images.

Workaround

Flicker

Although it happens sooner than the

Load

event _(

onload

)_, there is still a delay between when the page starts loading and when this event fires. This delay is the amount of time that it takes for the HTML content of the page itself to load. Greasemonkey injects user scripts at

DOMContentLoaded

time. Thus, there is a period of time when the page is loading, and may be showing on screen, before Greasemonkey has injected into the page. This delay is often known as flicker, where the page appears to load, then changes after a (usually) short delay.

top

Workaround

Generally, flicker is a problem that should be ignored. If, however, a script author decides that it must be avoided there is at least one technique.

Using a combination of userContent.css and @-moz-document() rules, the page can be hidden completely. The Greasemonkey script would then be crafted to undo this CSS rule, after altering it, thereby never showing the page in its pre-greased state.

top