Nesting a bunch of @imports is brutal for released code anyway, but it comes up a lot in dev situations with js libraries… Such a relief that somebody else was seeing this too.
Mostly for getting ie to support css3, png, etc.
Even Microsoft is excited to get rid of IE6.
A private collector?
IE8 leaks memory worse than IE6 ever did, yet I havent been able to find any mention of it. I say worse because: 1. No closures or circular reference are required. 2. I cannot find a workaround. …In case you missed it: every image element, anchor element, etc. added to a page uses memory that cannot be reclaimed even if the element is removed from the page. … Microsoft released the sixth preview of IE9 today. The leak is still there…
Can’t get enough of browser innards right now. Ha. “We hit a bit of a wall at one point when analysing the performance profiles, where there was a 1.5 second gap in the profile where it seemed like nothing was happening, but everything was paused with the CPU at 100%. We eventually discovered that there is a horrible bug in IE7 where if you have a :hover style on something that is not an anchor tag, it causes the rendering engine to go crazy, get all confused, and push the CPU up to 100% for no reason at all.”