3 ms·
I was working on an SPA around this time in an internal environment at a large bank. IE6 was the bane of my existence and the memory leaks in IE<8 made the app
by tracker1 8y ago
I was working on an SPA around this time in an internal environment at a large bank. IE6 was the bane of my existence and the memory leaks in IE<8 made the application unusable after being open for around 5 hours. The early solution was to close the application at lunch, the longer term was portable firefox and later an exception for Firefox proper for those users specifically, while IE8 exploration for support was in progress.
Around the same time, there was a Chrome in IE plugin that was also suggested for other applications but never got approved.
People complain about the progression/changes in JS since around 2010 (node, commonjs, es5+). But nothing is so bad as dealing with the really old browsers. IE6 was decent at release but became a boat anchor to the industry. Even then, you couldn't pay me enough to ever support IE4.x + NN4.x ever again.
Wonderful story.