Releases: Jarzka/stylefy
0.6.5
- stylefy/init immediately converts all font-faces, keyframes and custom classes in to CSS and adds the generated code in to DOM.
Previously, calling stylefy/init started requesting an animation frame to do the same process. However, it is useful to generate CSS code immediately so that font-faces, keyframes and custom classes are ready in the DOM before the first component is rendered.
0.6.4
0.6.3
- Return component style as inline style if the style definition contains hover state
Normally, when a style definition constains modes, the component is hidden until the generated CSS has been added to DOM. However, :hover mode does not change the initial state of the component, so it can be rendered with inline style until DOM is ready and class can be used.
0.6.2
0.6.1
0.6
- Uses a separate style tag for font-faces and keyframes.
This change was made because some browsers (Chrome) lose the font-face declaration when the style tag is updated. Since font-face and keyframes are not going to change, we keep them in a separate style tag which is not going to change.
0.5.5
- If style definition contains media queries or modes, {:visibility "hidden"} is returned.
This change has been made, because media queries and modes cannot be used in inline styles, so the components are probably going to be rendered incorrectly. It is better to hide them for the few milliseconds until DOM is ready.
0.5.2
- Added two new public Reagent atoms to core (font-faces-in-dom? & keyframes-in-dom?). This makes it possible to render components only when all font-faces and keyframes are added into DOM.
For example, IE11 requires that animation is present in DOM before it can be correctly used in a component.
0.5.1
0.5
- Adds support for @font-face and @Keyframes