internet explorer 8 does not support the textcontent property

If you only need to set text content and not retrieve, here's a trivial DOM version you can use on any browser it doesn't require either the IE innerText extension or the DOM Level 3 Core textContent property. I'd guess Safari and Opera also support this property. It is often possible to simply strip tags off of innerHTML of an element, rather than deal with all of the possible textContent/ innerText deviations.Īnother possibility, of course, is to walk the DOM tree and collect text nodes recursively.įirefox uses the W3C-compliant textContent property. defines new properties on elements, such as the textContent property that. You best bet is to first define your exact requirements and follow from there. Note The console object is not available in Internet Explorer 9 and older. I was playing with textContent abstraction (to work around these deficiencies), but it turned out to be rather complex. Internet Explorer is a compatibility solution, warns Jackson, rather than a browser that businesses should be using day to day for all web browsing activity. I have not been able to find a way to make this work IE at this time, due to a technical issue with the IE’s Matrix filter property (for those who want details, I use sizingMethodauto expand when using the Matrix filter which doesn’t support translations, and using sizingMethod’crop’ is not suitable to emulate the. Otherwise, innerText results in an empty string. Note: non-Explorer browsers support the translate function as well. Neither hidden (via style.display = 'none') nor orphaned from the document. In Safari, innerText functions properly only if an element is Var textNode = document.createTextNode('x') įinally, Safari 2.x also has buggy innerText implementation. This, for example, means that you can 'retrieve' textContent but not innerText from text nodes: var el = document.createElement('p') TextContent is part of Node interface, whereas innerText is part of HTMLElement. including SCRIPT contents (in fact, textContent and innerText in Opera seem to produce identical results, probably being just aliased to each other). Just to make things more entertaining, Opera - besides implementing standard textContent - decided to also add MSHTML's innerText but changed it to act as textContent - i.e. Note: The aria-describedby property is not designed to reference descriptions on an external. Second, and more importantly, textContent includes all of SCRIPT tag contents, whereas innerText doesn't. JAWS 8 and Window-Eyes 5.5+ partially support WAI-ARIA.

Update: I wrote a blog post detailing all the differences much better.įirefox uses W3C standard Node::textContent, but its behavior differs 'slightly' from that of MSHTML's proprietary innerText (copied by Opera as well, some time ago, among dozens of other MSHTML features).įirst of all, textContent whitespace representation is different from innerText one.

Internet explorer 8 does not support the textcontent property