Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a11y-addon: Parameters at story level affect other stories #8126

Closed
donaldpipowitch opened this issue Sep 19, 2019 · 9 comments
Closed

a11y-addon: Parameters at story level affect other stories #8126

donaldpipowitch opened this issue Sep 19, 2019 · 9 comments
Assignees

Comments

@donaldpipowitch
Copy link
Contributor

donaldpipowitch commented Sep 19, 2019

Describe the bug
a11y parameters at a story level affect other stories. Probably they aren't reseted correctly.

To Reproduce
https://github.com/donaldpipowitch/storybook-bug-demo-a11y-at-story-level

Expected behavior
a11y parameters at a story level should not affect other stories.

System:

  System:
    OS: macOS 10.14.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 10.16.0 - ~/.nvm/versions/node/v10.16.0/bin/node
    Yarn: 1.17.3 - ~/.yarn/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v10.16.0/bin/npm
  Browsers:
    Chrome: 76.0.3809.132
    Safari: 12.1.2
  npmPackages:
    @storybook/addon-a11y: ^5.2.1 => 5.2.1 
    @storybook/addons: ^5.2.1 => 5.2.1 
    @storybook/react: ^5.2.1 => 5.2.1 

Additional context
I actually wanted to configure one story with an unknown root element on purpose, because the a11y check was running very long. It would be nice if there would be an official way to disable the a11y check on a per story level or to disable the automatic run. Maybe something like { a11y: { manual: true } } which defaults to manual: false?

@donaldpipowitch
Copy link
Contributor Author

donaldpipowitch commented Oct 11, 2019

Wow, the stale bot got quicker. I eventually would like to fix this myself, but maybe just in one month or so to finish a previous project.

@stale stale bot removed the inactive label Oct 11, 2019
@shilman shilman added the todo label Oct 11, 2019
@storybookjs storybookjs deleted a comment from stale bot Oct 11, 2019
@shilman
Copy link
Member

shilman commented Oct 11, 2019

I've added the todo label (which tells the bot to go away) and assigned you! 😄

@donaldpipowitch
Copy link
Contributor Author

Would you be fine with the 'manual' setting as well? See "Additional context". That would be a new feature however, not just a bug fix.

@shilman
Copy link
Member

shilman commented Oct 13, 2019

@donaldpipowitch I like that idea. Any thoughts @CodeByAlex @jsomsanith-tlnd ?

@jsomsanith
Copy link
Contributor

Hi !
To disable an addon per story you have #6923.
But having an option to only run it manually would be awesome.

@donaldpipowitch
Copy link
Contributor Author

To disable an addon per story you have #6923.

@jsomsanith That's awesome. I never saw that setting before. Thank you. That is a good workaround for me until a "manual run" feature landed.

@shilman
Copy link
Member

shilman commented Nov 14, 2019

Gadzooks!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.3.0-alpha.45 containing PR #8779 that references this issue. Upgrade today to try it out!

You can find this prerelease on the @next NPM tag.

Closing this issue. Please re-open if you think there's still more to do.

@shilman
Copy link
Member

shilman commented Nov 30, 2019

Jeepers creepers!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.2.7 containing PR #8779 that references this issue. Upgrade today to try it out!

@shilman
Copy link
Member

shilman commented Jan 21, 2020

Ooh-la-la!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.0.0-alpha.0 containing PR #8883 that references this issue. Upgrade today to try it out!

You can find this prerelease on the @next NPM tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants