Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
The components are tested to work nearly perfect in all major browsers, including legacy browsers starting with IE8 (compatibility view OFF). Legacy browsers don't support CSS3 transitions and there is nothing we can/should do about that.
polyfill.js, designed for IE8-IE11. Most of these legacy browsers would require the polyfill.js in combination with HTML5 shims like so:
<script src="https://email@example.com/dist/polyfill.min.js"> </script> <!--[if lt IE 9]> <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> <![endif]-->
Along with a set of corrections, the required polyfills are:
dispatchEvent) and have been packed with the above mentioned polyfill.js.
For broader projects, a viable solution could be the minifill.js, which is mostly same as the provided polyfill but covering a wider range of features.
Finally an all-round polyfill solution is the Financial Times service:
As you can see the scripts rely on very few unsupported features, so starting with 0.9.8 versions, some polyfill dependencies have been removed for better usability and reach. Any of the above choice should do, but apparently legacy browsers perform better with the provided polyfill, and the reason why the automated service renders legacy browsers slow is still unknown.
Remember that the polyfill link(s) must be in your
<head>, especially the HTML5 shims, so that the legacy browsers can render the content properly. As for the provided polyfill, you can leave it there for all the browsers (IE 8-11 need
Event, Safari might need some corrections, etc); make sure you check the code from this example page here.