ie 6 sporadically does not run dj_load_init event

[guest]

broswer ie 6.0.2900 sp2

After several hours of testing our users are running into the situation where the widgets on the page stop working. After placing log points at several places in the code we noticed the dj_load_init function was not being run from the onreadystatechange event. This is a sporadic problem and can not be recreated on demand. Also memory does not appear to be a problem, we can shut down the all the browsers to clear memory, and the problem will continue when we start up again.

I believe this is the point of the offending code.

if (dojo.render.html.ie && dojo.render.os.win) {

document.attachEvent("onreadystatechange", function (e) {

if (document.readyState == "complete") {

dj_load_init();

}

});

}

[guest]

Replying to guest:

broswer ie 6.0.2900 sp2

After several hours of testing our users are running into the situation where the widgets on the page stop working. After placing log points at several places in the code we noticed the dj_load_init function was not being run from the onreadystatechange event. This is a sporadic problem and can not be recreated on demand. Also memory does not appear to be a problem, we can shut down the all the browsers to clear memory, and the problem will continue when we start up again.

I believe this is the point of the offending code.

if (dojo.render.html.ie && dojo.render.os.win) {

document.attachEvent("onreadystatechange", function (e) {

if (document.readyState == "complete") {

dj_load_init();

}

});

}

I'm sorry this is a 4.1 bug

[bill]

I haven't seen this bug. If it does occur it's obviously very important but since it's hard to reproduce I'm setting a 1.1 milestone.

[James Burke]

I'll set this for 1.0, but it really needs a test case. I believe Mark Wubben mentioned an issue with the init/load code running in IE when there was a specific Flash case involved.

If the reporter can give a test case, that would help immensely. Otherwise, I'll be closing the bug out, since this does seem hard to reproduce (I have not come across the issue, and neither have the teams that use Dojo 0.4.3).

[James Burke]

Closing this out, no test case.