Hi, > Use cases for dom:loaded VERSUS window.load are out of question, > right?
Oh, absolutely. There's a big difference between those two. :-) > Btw. Is it possible to remove img-Tags on dom:loaded, so that the > images aren't loaded? I'd recommend posting that question as a new, separate thread. -- T.J. On Apr 6, 3:34 pm, matths <matth...@dittgen.org> wrote: > You asked: "What's the use case? Between dom:loaded and window.load, > is there > really any need for body.load?" > > No, there's none. And it seems, that there ist an onLoad attribute for > the body HTML-tag as there is an onLoad attribute for each HTML > element in valid XHTML, but there is no onload event handler for body > in javascript. But there is an onload event handler for window, which > is fine. > > Use cases for dom:loaded VERSUS window.load are out of question, > right? > > Btw. Is it possible to remove img-Tags on dom:loaded, so that the > images aren't loaded? > I can't get this working for images in the markup, seems to work for > images loaded by the css, though. > Any ideas? > > Regards, > Matthias > > On Apr 1, 6:20 pm, "T.J. Crowder" <t...@crowdersoftware.com> wrote: > > > > > I'm still waiting for the use case, though. -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
