storybook-addon-pseudo-states
storybook-addon-pseudo-states copied to clipboard
CSS pseudo-classes for Storybook
**Vue 3.3.4, Tailwind 3.3.3, Storybook 7.4.1 and Pseudo-states 2.1.1** Hover states have disappeared from all our snapshots where we use this method: ``` parameters: { pseudo: { hover: ".showHover", },...
**Describe the bug** The hover behavior is still shown (while viewing the stories at issue on the canvas) even after switching between stories for a single React (v18.0.2) component. The...
Hi dear reader I tried to hover on a element and then check if another element is being displayed to the user or not, but then I realized that it...
The core storybook plugins use regular dependencies but this package is using peerDependencies. For example: https://github.com/storybookjs/storybook/blob/next/addons/actions/package.json It seems like it would be nicer to follow their example as that makes...
In CSS, classnames may have colons (`:`). Tailwind CSS uses a state followed by a colon to express a utility class that only applies when that state is active (see...
https://developer.chrome.com/blog/new-in-chrome-90/#declarative
Frameworks such as Tailwind can introduce stylesheets with a large number of selectors, and at the moment this addon has a hard 1000-selector limit before it stops iterating. This PR...
If you install this plugin with the `@next` to support storybook 7, the components that rely on chakra stop rendering correctly after `build-storybook`. I've created a reproduction repo https://github.com/wladiston/chakra-sb7-bug-repro Just...
In `package.json` it specifies these paths: https://github.com/chromaui/storybook-addon-pseudo-states/blob/main/package.json#L17 https://github.com/chromaui/storybook-addon-pseudo-states/blob/main/package.json#L18 However, those paths do not exist in the published module. Instead, `preset.js` is at the root level of the package.
I don't know if this qualifies as a pseudo state, but it would be great to see what an element looks like disabled (namely buttons).