This document describes the Internet Explorer (IE) idiosyncrasies when dealing with custom HTML attributes and tags. Read this document if you are planning on deploying your Angular application on IE.
The project currently supports and will attempt to fix bugs for IE9 and above. The continuous integration server runs all the tests against IE9, IE10, and IE11. See Travis CI and ci.angularjs.org.
We do not run tests on IE8 and below. A subset of the AngularJS functionality may work on these browsers, but it is up to you to test and decide whether it works for your particular app.
To ensure your Angular application works on IE please consider:
ng-style
tags instead of style="{{ someCss }}"
. The latter works in Chrome, Firefox,
Safari and Edge but does not work in Internet Explorer (even 11).type
attribute of buttons, use ng-attr-type
tags instead of
type="{{ someExpression }}"
. If using the latter, Internet Explorer overwrites the expression
with type="submit"
before Angular has a chance to interpolate it.value
attribute of progress, use ng-attr-value
tags instead of
value="{{ someExpression}}"
. If using the latter, Internet Explorer overwrites the expression
with value="0"
before Angular has a chance to interpolate it.placeholder
attribute of textarea, use ng-attr-placeholder
tags instead
of placeholder="{{ someExpression }}"
. If using the latter, Internet Explorer will error
on accessing the nodeValue
on a parentless TextNode
in Internet Explorer 10 & 11
(see issue 5025).