@@ -12,12 +12,12 @@ on IE v8.0 or earlier.
12
12
13
13
To make your angular application work on IE please make sure that:
14
14
15
- 1. You provide JSON.stringify (via
16
- [Douglas Crockford's JSON2 library ](https://github.com/douglascrockford/JSON-js), or similar)
17
- if the browser does not have it. IE7 and earlier will need this.
15
+ 1. You polyfill JSON.stringify if necessary (IE7 will need this). You can use
16
+ [JSON2 ](https://github.com/douglascrockford/JSON-js) or
17
+ [JSON3](http://bestiejs.github.com/json3/) polyfills for this.
18
18
19
- 2. you **do not** use custom element tags such as `<ng:view>` (use the attribute version `<div
20
- ng-view>` instead), or
19
+ 2. you **do not** use custom element tags such as `<ng:view>` (use the attribute version
20
+ `<div ng-view>` instead), or
21
21
22
22
3. if you **do use** custom element tags, then you must take these steps to make IE happy:
23
23
@@ -29,7 +29,7 @@ To make your angular application work on IE please make sure that:
29
29
document.createElement('ng-include');
30
30
document.createElement('ng-pluralize');
31
31
document.createElement('ng-view');
32
-
32
+
33
33
// Optionally these for CSS
34
34
document.createElement('ng:include');
35
35
document.createElement('ng:pluralize');
@@ -71,7 +71,7 @@ categories, and each category has its own fix.
71
71
72
72
## The Good News
73
73
74
- The good news is that these restrictions only apply to element tag names, and not to element
74
+ The good news is that these restrictions only apply to element tag names, and not to element
75
75
attribute names. So this requires no special handling in IE: `<div my-tag your:tag></div>`.
76
76
77
77
@@ -137,7 +137,7 @@ The to make CSS selector work with custom elements the custom element name must
137
137
<script>
138
138
// needed to make ng-include parse properly
139
139
document.createElement('ng-include');
140
-
140
+
141
141
// needed to enable CSS reference
142
142
document.createElement('ng:view');
143
143
</script>
0 commit comments