Hi, > It's not already been fired! > Evidence: If I put an onload attribute directly into the html markup > which alerts "onLoad", the alert is seen AFTER the "DOM.ready" alert.
That's evidence that the DOM0 event is fired at that point; I wouldn't guarantee that the two are fired at the same time. They certainly *should* be. I'm still waiting for the use case, though. -- T.J. On Apr 1, 2:44 pm, matths <[email protected]> wrote: > Hi, > > > > Doesn’t work – the alert is not displayed. But why? > > > Because by the time you've hooked the event, it's (probably) already > > been fired, so your handler never gets fired. > > It's not already been fired! > Evidence: If I put an onload attribute directly into the html markup > which alerts "onLoad", the alert is seen AFTER the "DOM.ready" alert. > > > (Are you the same person as the OP?) > > no, he's not. > > Matthias -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
