也可以在其他浏览器中模拟innerText行为:

 if (((typeof window.HTMLElement) !== "undefined") && ((typeof HTMLElement.prototype.__defineGetter__) !== "undefined")) {
     HTMLElement.prototype.__defineGetter__("innerText", function () {
         if (this.textContent) {
             return this.textContent;
         } else {
             var r = this.ownerDocument.createRange();
             r.selectNodeContents(this);
             return r.toString();
         }
     });
     HTMLElement.prototype.__defineSetter__("innerText", function (str) {
         if (this.textContent) {
             this.textContent = str;
         } else {
             this.innerHTML = str.replace(/&/g, '&amp;').replace(/>/g, '&gt;').replace(/</g, '&lt;').replace(/\n/g, "<br />\n");
         }
     });
 }

只是从原帖子下的评论中转发。innerHTML适用于所有浏览器。谢谢stefita。

myElement。innerHTML = "foo";

从2016年的Firefox v45开始，innerText在Firefox上工作，看看它的支持:http://caniuse.com/#search=innerText

如果希望它能在以前版本的Firefox上运行，可以使用textContent，它在Firefox上有更好的支持，但在较旧的IE版本上更差:http://caniuse.com/#search=textContent

jQuery提供了一个.text()方法，可以在任何浏览器中使用。例如:

$('#myElement').text("Foo");

innerText已经添加到Firefox，应该在FF45版本中可用:https://bugzilla.mozilla.org/show_bug.cgi?id=264412

规范草案已经编写完成，并有望在未来被纳入HTML生活标准:http://rocallahan.github.io/innerText-spec/， https://github.com/whatwg/html/issues/465

请注意，目前Firefox、Chrome和IE实现都是不兼容的。展望未来，我们可能会看到Firefox、Chrome和Edge融合在一起，而旧的IE仍然不兼容。

参见:https://github.com/whatwg/compat/issues/5

注意，在谷歌Chrome中，Element::innerText属性将不包含被CSS样式“display:none”隐藏的文本(以及它将删除被其他CSS技术掩盖的内容(包括font-size:0, color:transparent，以及其他一些导致文本不以任何可见方式呈现的类似效果)。

其他CSS属性也被考虑:

First the "display:" style of inner elements is parsed to determine if it delimits a block content (such as "display:block" which is the default of HTML block elements in the browser's builtin stylesheet, and whose behavior as not been overriden by your own CSS style); if so a newline will be inserted in the value of the innerText property. This won't happen with the textContent property. The CSS properties that generate inline contents will also be considered : for example the inline element <br \> that generates an inline newline will also generate an newline in the value of innerText. The "display:inline" style causes no newline either in textContent or innerText. The "display:table" style generates newlines around the table and between table rows, but"display:table-cell" will generate a tabulation character. The "position:absolute" property (used with display:block or display:inline, it does not matter) will also cause a line break to be inserted. Some browsers will also include a single space separation between spans

但是Element::textContent仍然包含独立于应用CSS的内部文本元素的所有内容，即使它们是不可见的。textContent中不会生成额外的换行符或空格，它只是忽略了内部元素的所有样式和结构以及内联/块或定位类型。

使用鼠标选择的复制/粘贴操作将丢弃放在剪贴板中的纯文本格式的隐藏文本，因此它不会包含textContent中的所有内容，而只包含innerText中的内容(如上所述，在空格/换行生成之后)。

这两个属性然后在谷歌Chrome支持，但他们的内容可能会有所不同。旧的浏览器仍然包含在innetext的一切，就像textContent现在所包含的(但他们的行为与当时产生的空白/换行符是不一致的)。

jQuery将通过将".text()"方法添加到它通过$()查询返回的已解析元素中来解决浏览器之间的这些不一致。在内部，它通过查看HTML DOM来解决困难，只处理“节点”级别。它会返回一些看起来更像标准textContent的东西。

需要注意的是，这个jQuery方法不会插入任何额外的空格或换行符，这些空格或换行符可能是由内容的子元素(如<br />)引起的，在屏幕上可见。

如果您设计了一些可访问性脚本，并且您的样式表解析为非听觉呈现，例如用于与盲文阅读器通信的插件，如果它必须包括特定的标点符号，这些标点符号被添加到具有“display:none”样式的span中，并且通常包含在页面中(例如上标/下标)，则该工具应该使用textContent，否则在盲文阅读器上innerText将非常混乱。

Texts hidden by CSS tricks are now typically ignored by major search engines (that will also parse the CSS of your HTML pages, and will also ignore texts that are not in contrasting colors on the background) using an HTML/CSS parser and the DOM property "innerText" exactly like in modern visual browsers (at least this invisible content will not be indexed so hidden text cannot be used as a trick to force the inclusion of some keywords in the page to check its content) ; but this hidden text will be stil displayed in the result page (if the page was still qualified from the index to be included in results), using the "textContent" property instead of the full HTML to strip the extra styles and scripts.

IF you assign some plain-text in any one of these two properties, this will overwrite the inner markup and styles applied to it (only the assigned element will keep its type, attributes and styles), so both properties will then contain the same content. However, some browsers will now no longer honor the write to innerText, and will only let you overwrite the textContent property (you cannot insert HTML markup when writing to these properties, as HTML special characters will be properly encoded using numeric character references to appear literally, if you then read the innerHTML property after the assignment of innerText or textContent.