storybook-addon-pseudo-states
storybook-addon-pseudo-states copied to clipboard
chromaui
CSS pseudo-classes for Storybook
Old: New: Working on improving state replacement for web components.
Exact error received: ``` withPseudoState.js:178 DOMException: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule '.MuiButtonGroup-root > :focus, .pseudo-focus .MuiButtonGroup-root > { z-index: 2; }' ``` Input selector:...
The first time works fine  But after we change any input option, the status is never updated 
Trying to fix #90 To reproduce the issue, go from `Example/Button/Hover` to `Example/Button/Default` and see how the hover state persist. (Not sure how this affects the shadow host)
Although the addon still seems to work it gives a warning in Storybook 8 as it depends on an earlier version. Might want to add it [here](https://github.com/storybookjs/storybook/issues/26031) as well.
I use the sass react component in storybook. Everything works fine with storybook-addon-pseudo-states. But after manual edit the webpack finals process. The state display broken.. I just replaced the @storybook/preset-scss...
We have an element that uses a `:not(:focus)` rule with visually-hidden styling. This works fine in production but in Storybook the rules are almost always applied. I was hoping [v3.1.1](https://github.com/chromaui/storybook-addon-pseudo-states/pull/115)...
## Problem Given this element style: ```css main-container:is(:hover, :focus) .tooltip { opacity: 1; } ``` Writing a story that activates `hover` or `focus` styles do not apply. ```html ``` ##...
The addon currently does not have a version that allows Storybook 9 in its peer dependency range.
Using `storybook` 8.3.5 / `storybook-addon-pseudo-states` 4.0.2 (also an issue in 3.1.1). ## Problem Our typography system has this CSS (only relevant parts shown): ``` .textLink:where(:focus-visible) { /* specificity 0-1-0 --...
