internet explorer 8 does not support the textcontent property

So, with Internet Explorer 8 (IE8), we added IE8 standards, but also kept Internet Explorer 7 (IE7) standards. Getting modern was opt-in because that was easier.įast forward, as Internet Explorer standards mode supported more and more standards, we decided not to just update the mode we called standards mode because, when we did, we risked breaking applications written for an older interpretation of the standards. Which meant, if your tool didn’t add this in, you would get Internet Explorer 5 emulation (quirks mode) by default. So, what really happened is that developer tools either added this in the skeleton code, or they didn’t. So, it wasn’t just the presence or absence of a declaration, but also whether you put in a correctly formatted and properly chosen DTD, that would promote you to standards mode. You see, in the bad old days, you couldn’t just put in, you had to put in a full document type definition (DTD), and what you put in determined whether you’d get standards or quirks. This, of course, had one little pesky problem: most people neither manually type HTML nor obsessively read the documentation to make sure they get the right DOCTYPE. All existing content (which had no DOCTYPE) would get quirks mode you got standards mode by adding a specific DOCTYPE. “quirks mode” comes from this “easy button” approach.

Looking all the way back to Internet Explorer 6, the very concept of “standards mode” vs. In the past, Internet Explorer was optimized for simplicity at the expense of technical debt. (For example, if you’ve disabled User Account Control, require a 32-bit OS or 32-bit Office suite, or are paying for extended support for a legacy version of Java, you have some technical debt.) But this technical debt? Well, it’s different. It’s true that most organizations have some technical debt lying around. In short, this seems like a deliberate decision to take on some technical debt. As a result, it can seem that using Internet Explorer be default for all situations is the “easy button” because, well, most of your sites were designed for Internet Explorer, so…just…always use it, ok? In healthcare (as in many other industries), it’s often the case that you’re running with an extremely thin team. įrom time to time, I am asked by customers, “How do I ensure that all web traffic goes to Internet Explorer?” In fact, I was recently asked this question by someone trying to help a hospital. Internet Explorer is still a component of Windows and follows the support lifecycle of the OS on which it’s installed.

We are committed to keeping Internet Explorer a supported, reliable, and safe browser. Update March 12, 2019: Since this post was published, I’ve received some customer questions on the future of Internet Explorer.

Internet explorer 8 does not support the textcontent property