Closed GoogleCodeExporter closed 8 years ago
Sorry, meant to say "I expect the library to run the existing onunload handler
AFTER
doing the onunload cleanup that it needs to do."
Original comment by xan...@gmail.com
on 2 Oct 2007 at 6:18
[deleted comment]
[deleted comment]
[deleted comment]
Xander, thanks for the suggested patch. I ended up fixing this with a fairly
standard
cross-browser event registration method. There's no way to guarantee execution
order
of unload events registered this way, but I don't think it should matter. I
can't
imagine a scenario where somebody would be relying on a non-null value for
dhtmlHistory.firstLoad during their own custom unload events.
Original comment by bdpathfi...@gmail.com
on 7 Nov 2007 at 9:25
Original issue reported on code.google.com by
xan...@gmail.com
on 2 Oct 2007 at 6:13