Releases: LeaVerou/style-observer
Releases · LeaVerou/style-observer
v0.1.1
What's Changed
Improvements
- Make the Style Observer package work correctly in Webpack by @web-padawan in #122.
- Detect the Safari adopted stylesheet bug and work around it by @DmitrySharabin and @LeaVerou in #121 and #124.
Tests
- Skip Shadow DOM tests in browsers that don't support them by @DmitrySharabin in #123.
New Contributors
- @web-padawan made their first contribution in #122
Changes in previous releases
v0.1.0
Optimizations
- Use adopted stylesheets (if supported) for shadow root hosts instead of inline styles (by @LeaVerou in #110; tests by @DmitrySharabin in #112).
Bugfixes
- Do not break in DOM-less environments, like NodeJS (by @benface in #115).
- Setting
transition-property: none
should not stop properties observation (by @LeaVerou in 3a0f0d9 and @DmitrySharabin in #118).
TypeScript
- Make options optional in
StyleObserver()
andElementStyleObserver()
constructors (by @LeaVerou in f14bb02). - Add type overloads for
observe()
andunobserve()
so that TypeScript allows providing their arguments in any order (by @LeaVerou in 151b0c2 and @DmitrySharabin in #116).
New Contributors
v0.0.9
- Set
allow-discrete
(if supported) for observed properties only by @DmitrySharabin in #106.
v0.0.8
- Set
transition-behavior
in a constructed stylesheet by @DmitrySharabin in #100.
Full Changelog: 0.0.7...0.1.1
v0.0.7
Big improvements in this release! Style-observer now detects a lot more cases:
- Changes due to moving an element to another place in the DOM are now detected
- Shadow DOM: Changes due to a slotted element's slot going from nonexistent to existing
- Changes to the
display
property are now correctly detected in all browsers - Changes that happened when an element was disconnected from the DOM will now be detected once it becomes connected again
- Better integration with TypeScript
Full Changelog: 0.0.6...0.0.7