- Removed
element.closest()
polyfill as it's not needed anymore. - Removed
getMatchedCSSRules
polyfill since it's dreadfully slow and Chrome is depreciating it in Chrome 41. It seems thatgetComputedStyle
is close enough for my purposes. - Moved the resize event handler to a global level, reducing the number of listeners when a large number of elements are replaced
- Added default style caching for image elements. It assumes that the image retrieved won't change during this session. This drastically speeds up when replacing multiple elements with the same image.
- Filters out CSS2Property things that can cause Firefox 31 to error out on.
- Changed to a scanning model when elements are inserted. The previous model would miss deeply nested elements that would've matched had it looked. This also allows for multiple mutations to occur before processing them in a vague attempt to keep somewhat 'responsive'.
- Use external
element.closest()
polyfill via npm (#30), small performance win - Use external rAF polyfill via npm (#30)
- Optimize Performance (+28%) (#22)
- Add option
disableCrossDomain: 'true'
to ignore external stylesheets (CORS/CSP) (#7, #15)
- Update README with latest browser developments
- Don’t test for
matchMedia
when it isn’t supported (#22) - Update usage of indexed style properties regarding latest Firefox implementation
- Remove unnneeded postinstall script in npm (#14).
- Fixed a few minor code issues
- Update polyfill.rAF.js to not include moz prefix anymore
- Minor update on the getMatchedCSSRule.js
- Re-indented the files, stick to code style
- Use utf-8 in test html
- Added correct path for 'main'
- Fix array-detection of arguments in `objectFill.init (#10) thanks to @xax
- Extended fix for Firefox (#5)
- Fix for Firefox
- Add AMD definition in core JavaScript
- Enabled polyfill to initialize after load when being fetched asynchronously
- Initial Release