[removed] vs <body onload=“”/>
What exactly is the difference between the window.onload event and the onload event of the body tag? when do I use which and how shoul
-
Think of onload like any other attribute. On an input box, for example, you could put:
<input id="test1" value="something"/>Or you could call:
document.getElementById('test1').value = "somethingelse";The onload attribute works the same way, except that it takes a function as its value instead of a string like the value attribute does. That also explains why you can "only use one of them" - calling window.onload reassigns the value of the onload attribute for the body tag.
Also, like others here are saying, usually it is cleaner to keep style and javascript separated from the content of the page, which is why most people advise to use window.onload or like jQuery's ready function.
讨论(0) -
window.onload = myOnloadFuncand<body onload="myOnloadFunc();">are different ways of using the same event. Usingwindow.onloadis less obtrusive though - it takes your JavaScript out of the HTML.All of the common JavaScript libraries, Prototype, ExtJS, Dojo, JQuery, YUI, etc. provide nice wrappers around events that occur as the document is loaded. You can listen for the window onLoad event, and react to that, but onLoad is not fired until all resources have been downloaded, so your event handler won't be executed until that last huge image has been fetched. In some cases that's exactly what you want, in others you might find that listening for when the DOM is ready is more appropriate - this event is similar to onLoad but fires without waiting for images, etc. to download.
讨论(0) -
window.onload- Called after all DOM, JS files, Images, Iframes, Extensions and others completely loaded. This is equal to $(window).load(function() {});body onload=""- Called once DOM loaded. This is equal to $(document).ready(function() {});讨论(0) -
If you're trying to write unobtrusive JS code (and you should be), then you shouldn't use
<body onload="">.It is my understanding that different browsers handle these two slightly differently but they operate similarly. In most browsers, if you define both, one will be ignored.
讨论(0) -
There is no difference ...
So principially you could use both (one at a time !-)
But for the sake of readability and for the cleanliness of the html-code I always prefer the window.onload !o]
讨论(0) -
There is no difference, but you should not use either.
In many browsers, the
window.onloadevent is not triggered until all images have loaded, which is not what you want. Standards based browsers have an event calledDOMContentLoadedwhich fires earlier, but it is not supported by IE (at the time of writing this answer). I'd recommend using a javascript library which supports a cross browser DOMContentLoaded feature, or finding a well written function you can use. jQuery's$(document).ready(), is a good example.讨论(0)
加载中...
- 热议问题