You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just attempted to run my app that uses Plates in IE8 and it blew up. I noticed pull request #53 makes plates more compatible with ES3, so I thought Plates might work in IE8.
Is there already support for IE7/IE8? If not, is it something that is planned? If there is support, what shims are required to make it work? My application needs to support IE7+, and I'm trying to determine how much effort will be involved to use Plates.
I'm already using this style of accessing reserved words:
This was one of the first things that hit me as well when I started testing Plates for cross browser compatibility. To tackle this issue I have added a map#className alias which maps directly to map#class.
This fix should land in master soon, so I thought I'd give you and heads up on this :)
- Added new polyfills for array#indexOf
- Exposed the Array.isArray in the sameway as the other polyfill
- Now using charAt instead of html[i] as that doesn't work in older browsers
- Wrapped the className alias in quotes as it broke in IE again.
- Updated the browser unit test with some extra polyfills and line break removers
- Updated the browser tests with the new className API instead of class
There is now an alias for class, if you need IE7/8 support you can use map.className instead of map.class. The alias landed in master, so I'm closing this. All other IE related issues are solved in master.
I just attempted to run my app that uses Plates in IE8 and it blew up. I noticed pull request #53 makes plates more compatible with ES3, so I thought Plates might work in IE8.
Is there already support for IE7/IE8? If not, is it something that is planned? If there is support, what shims are required to make it work? My application needs to support IE7+, and I'm trying to determine how much effort will be involved to use Plates.
I'm already using this style of accessing reserved words:
Instead of this:
The text was updated successfully, but these errors were encountered: