No, unfortunately the order is till not preserved for DOM:LOADED event.
Thank you for your suggestion.
2010/4/15 Mislav Marohnić
> I think that "dom:loaded" handlers should execute in order, since it's a
> custom event. Try those instead of "load".
>
> document.on("dom:loaded", function(){ ... }
> In any case, I don't think it would be a fix
Well, that's a shame. I know that browsers do not gurantee the order in
which the event handlers execute, but it is such a convinient and
straightforward approach to do so, isn't it. That is why Firefox, Opera and
all the best browsers embraced it. IE
Sorry for being impoly, never thought I would get somebody's attention to my
letter. It's just very frustraiting "bug" for me and I was very dissapointed
to not see the change in the new version of Prototype. Thank you for your
attention.
2010/4/15 Johan Arensman
> Hello... Dziamid,
>
> Please t
Well, to be honest, I've been focusing on Firefox and Opera mainly when
developing software and never even thought that order is not guaranteed,
before the task to support IE arrived! So there is plenty of code to
refactor, which is very frustrating. I know that relying on event order
isn't a best
