4 ms·
tl;dr Internet Explorer introduced a nonstandard mechanism, x.innerText, that returned the 'plaintext representation' of some node tree, in contrast to x.textCo
by Nzen 6y ago
tl;dr Internet Explorer introduced a nonstandard mechanism, x.innerText, that returned the 'plaintext representation' of some node tree, in contrast to x.textContent (which includes the source whitespace) or selection.toString (which takes longer). This article looks at the use case, compares then browser compatibility (including jQuery), and looks at some previous standardization efforts.