angular-cn/aio/content/examples/setup/src
Georgios Kalpakas 4f37f86433 fix(aio): switch from `innerText` to `textContent` to support older browsers
`innerText` is not supported in Firefox prior to v45. In most cases (at least
the ones we are interested in), `innerText` and `textContent` work equally well,
but `textContent` is more performant (as it doesn't require a reflow).

From [MDN][1] on the differences of `innerText` vs `textContent`:

> - [...]
> - `innerText` is aware of style and will not return the text of hidden
>   elements, whereas `textContent` will.
> - As `innerText` is aware of CSS styling, it will trigger a reflow, whereas
>   `textContent` will not.
> - [...]

[1]: https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent#Differences_from_innerText

Fixes #17585
2017-06-19 10:32:36 -07:00
..
app fix(aio): switch from `innerText` to `textContent` to support older browsers 2017-06-19 10:32:36 -07:00
index.html docs(aio): update migrated content from anguar.io 2017-03-28 10:21:46 +01:00
main.ts docs(aio): update migrated content from anguar.io 2017-03-28 10:21:46 +01:00
quickstart-specs.html docs(aio): update migrated content from anguar.io 2017-03-28 10:21:46 +01:00
systemjs.config.extras.js docs(aio): update migrated content from anguar.io 2017-03-28 10:21:46 +01:00