@@ -12,12 +12,12 @@ on IE v8.0 or earlier.
1212
1313To make your angular application work on IE please make sure that:
1414
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.
1818
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
2121
2222 3. if you **do use** custom element tags, then you must take these steps to make IE happy:
2323
@@ -29,7 +29,7 @@ To make your angular application work on IE please make sure that:
2929 document.createElement('ng-include');
3030 document.createElement('ng-pluralize');
3131 document.createElement('ng-view');
32-
32+
3333 // Optionally these for CSS
3434 document.createElement('ng:include');
3535 document.createElement('ng:pluralize');
@@ -71,7 +71,7 @@ categories, and each category has its own fix.
7171
7272## The Good News
7373
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
7575attribute names. So this requires no special handling in IE: `<div my-tag your:tag></div>`.
7676
7777
@@ -137,7 +137,7 @@ The to make CSS selector work with custom elements the custom element name must
137137 <script>
138138 // needed to make ng-include parse properly
139139 document.createElement('ng-include');
140-
140+
141141 // needed to enable CSS reference
142142 document.createElement('ng:view');
143143 </script>
0 commit comments