Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix for #5198, event memory leak limited to IE only via conditional c…
…ompilation
- Loading branch information
1 parent
4a3c4c8
commit f3474c0
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
f3474c0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And that's how fairytale story about feature over browser detection ends :-)
f3474c0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't be silly. That is old code. They have since replaced it with feature detection for IE's DOM API and test for the Firefox bug in a different way. By reworking the event system a bit they could make the event system not rely on unload for IE as well.
f3474c0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really? I suppose unload event is necessary and feature undetectable as well.
f3474c0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unload is not necessary if the event system is tweaked a bit. Most libs use the
unload
event to cleanup memory leaks in IE6/7. Absent tweaking the event system to remove the need forunload
they use DOM API inference to detect IE's non-standard event and use theunload
event for it.