Since I expect it to be a race condition (pushing up the script node which registered the function for "dom:loaded" some lines in the html- source fixed the problem), and since it is only reproducable on certain hardware/software-environments, producing a pared-down example could take very long. I do not know if anybody in our team will find so much time to spend on a pared-down race condition example hunt, which can take an unpredictable amount of time, because we are no browser-engine experts.
This is meant as a trigger for the developers of prototype. So we if the idea of a race condition in IE (finishing rendering of the DOM- >triggering dom:loades vs. JS-execution of a register-call) is not something that triggers a thought for the prototype-developers, we have to wait if somebody comes up with more convincing example. Sorry that we can not help further. And thanks for your patience ;-) Alex On Sep 2, 12:26 pm, "T.J. Crowder" <[email protected]> wrote: > Hi, > > That's not a "...pared-down, self-contained example..." Please have a > look at Step 3 at the link[1] again, there's a _reason_ for going > through the process of creating the pared-down example. > > [1]http://proto-scripty.wikidot.com/faq#xyzprob > -- > T.J. Crowder > tj / crowder software / comwww.crowdersoftware.com > > On Sep 2, 11:21 am, Alexander Knöller <[email protected]> > wrote: > > > Hi. > > > Until tomorrow you can reproduce it with IEs and fitting hardware/ > > software-environments. (On a virtualBox-installation on a macosX I > > could not reproduce it, on an Ubuntu with VMWare a colleage could, > > another could with a native Installation): > > Tryhttp://www.jungstil.de/akn/bundle.htm?bu=2023439 > > several times. > > Each time try to click "Artikel auf den Wunschzettel". > > Often it works. Sometimes you get an JS-Error because of missing > > references. > > > From tomorrow morning on there will be a fix, which executes the JS- > > Code directly instead of registering it as a function for > > "dom:loaded". > > > On Sep 1, 9:37 am, "T.J. Crowder" <[email protected]> wrote: > > > > Hi, > > > > Can you pick up with #3 on this list: > > > >http://proto-scripty.wikidot.com/faq#xyzprob > > > > ...and post the result (unless you figure it out in the meantime)? > > > -- > > > T.J. Crowder > > > tj / crowder software / comwww.crowdersoftware.com > > > > On Aug 31, 2:35 pm, Alexander Knöller <[email protected]> > > > wrote: > > > > > Hi there. > > > > > We register some calls for the dom:loaded-event in the HTML-BODY. > > > > Depending on the runtime environment (hardware/Windows version) > > > > sometimes the page produces in both IE-Versions JS-errors, because > > > > some or all registered functions were never called and so some > > > > references are missing for later actions. > > > > The more the JS-Script-node for the event registration is pushed > > > > upward in the html-source, the less probable this error occurs until > > > > it disappears completely for our test environment. > > > > Our guess is, the dom:loaded event is fired before the event > > > > registration-JS-code has finished. > > > > > Of course a workaround is to put this kind of event registration in > > > > the HEAD-section, but I did not find a direct statement in the > > > > documentation mentioning this as a requirement. > > > > > Does anybody know about this effect/problem? > > > > > Thanx --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
