4 ms·
From my experience, the next IE6 is IE7/IE8. They both have the strangest quirks. (as a random example, in IE7, try setting the hash of an iframe, from an ifra
by threepointone 15y ago
From my experience, the next IE6 is IE7/IE8. They both have the strangest quirks.
(as a random example, in IE7, try setting the hash of an iframe, from an iframe inside of that, and if they're on different domains. It... opens up a new window?! And the fix for this is to have another iframe inside that inner iframe which is the same domain as the iframe you want to set the hash on, and from that, do parent.parent.location='#whatever'; %^$^&$#@$&)
(and in IE8, WHY does postMessage not work properly across popups opened up from iframes? WHY.)
Bah.
- yuhong 15y agoBut more often mentioned is the lack of support for HTML5 and CSS3.
- ZoFreX 15y agoIt's obviously going to be IE8. Anyone can upgrade from 7 to 8, but to upgrade to 9 you have to be running something more modern than XP, which isn't going away anytime soon.
- T-hawk 15y agoIndeed. XP itself is a major reason IE6 hangs around so much. XP installation discs and images only ever came with IE6, never anything newer. And with the frequency that most corporate workstations get reassigned and recreated and reinstalled, IE6 comes out of its casket all the time. It's not that these corps are scared or ignorant of upgrading past IE6, it's that doing so across 100 or 10,000 machines is a huge task and not worthwhile from a cost-benefit standpoint.
- ZoFreX 15y agoHave you ever worked in that sort of environment? "doing so across 100 or 10,000 machines is a huge task and not worthwhile from a cost-benefit standpoint" contradicts my own experiences.
- yuhong 15y agoAFAIK IE 5.01 on Windows 2000 was supported until the end of support of Win2000, despite the fact it was dying by 2005 or so, exactly because it was bundled with Win2000.