R
ReGenesis0
I'm trying to rewrite the existing window using javascript. This
works fine in IE- but in Mozilla, after I call a window.open, Mozilla
starts wandering around like an alshiemers patient and bumping into
doors.
Specificly, Mozilla seems to be losing my... functions. Or
variables. Except, I've tried alerts with dummy variables, and it
seems to find THEM just fine...
Does Mozilla start unloading existing memory right after a
document.open call? As currently structured, my script calles an open,
then skips aroudn through functions, performing a series of
document.writes before closing.
Would this problem go away if instead of performing that nonlinear
series of writes, it performed a series of additions to a string and I
just did one open/write/close at the end? (Doign so would be a neither
major nor minor alteration, so I'm asking before attempting it.)
Theological question: Who is 'right' here against the ruler of how
javascript is SUPPOSED to perform? Have I simply been benefittign from
IE's tardy/nonexistant memory cleanup, or is Mozilla overeager?
(assuming, again, it is memory cleanup I'm running into.)
Any help appreciated. I don't think I'm using anything beyond
Javascript 1.2.
-Derik
works fine in IE- but in Mozilla, after I call a window.open, Mozilla
starts wandering around like an alshiemers patient and bumping into
doors.
Specificly, Mozilla seems to be losing my... functions. Or
variables. Except, I've tried alerts with dummy variables, and it
seems to find THEM just fine...
Does Mozilla start unloading existing memory right after a
document.open call? As currently structured, my script calles an open,
then skips aroudn through functions, performing a series of
document.writes before closing.
Would this problem go away if instead of performing that nonlinear
series of writes, it performed a series of additions to a string and I
just did one open/write/close at the end? (Doign so would be a neither
major nor minor alteration, so I'm asking before attempting it.)
Theological question: Who is 'right' here against the ruler of how
javascript is SUPPOSED to perform? Have I simply been benefittign from
IE's tardy/nonexistant memory cleanup, or is Mozilla overeager?
(assuming, again, it is memory cleanup I'm running into.)
Any help appreciated. I don't think I'm using anything beyond
Javascript 1.2.
-Derik