Skip to content

Releases: Jarzka/stylefy

0.6.5

02 Jun 18:53
Compare
Choose a tag to compare
  • 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

02 Jun 18:23
Compare
Choose a tag to compare
  • Makes it possible to define custom classes with custom names.

Useful when working with 3rd party libraries / frameworks. use-style should still be used when ever possible.

0.6.3

23 May 14:46
Compare
Choose a tag to compare
  • 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

23 May 14:20
Compare
Choose a tag to compare
  • Fixed invalid error logging

0.6.1

22 May 20:31
Compare
Choose a tag to compare
  • When returning invisible component, also return the given style properties

This helps the component to take all the space it's going to need

0.6

22 May 20:20
Compare
Choose a tag to compare
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

22 May 19:54
Compare
Choose a tag to compare
  • 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

22 May 18:02
Compare
Choose a tag to compare
  • 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

22 May 17:33
Compare
Choose a tag to compare
  • DOM is updated immidiately after font-faces or keyframes are defined

0.5

22 May 17:07
Compare
Choose a tag to compare
0.5