You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just noticed that my own component's story which uses <section> was picking up those styles:
Head:
Component affected:
I can just delete the examples, and all is well. Not a high priority problem. It does raise the question though, why would that be required? Can that initial import be a scoped page.module.css to avoid having to remove docs that are helpful to new developers in the future?
To Reproduce
Interestingly, I can't reproduce using a basic stack blitz, even clicking through to Page and back to ComponentA doesn't have the effect. It's reliable on my local though.
lancegliser
changed the title
[Bug]: React + Storybook example story component imports unscoped css
[Bug]: React + Storybook + Vite example Page component css can leak
Aug 16, 2023
lancegliser
changed the title
[Bug]: React + Storybook + Vite example Page component css can leak
[Bug]: React + Storybook + Vite example component Page.css can leak
Aug 16, 2023
Describe the bug
The example src/stories/Page.tsx component includes this at the top:
The contents of
page.css
are:I've just noticed that my own component's story which uses
<section>
was picking up those styles:Head:
Component affected:
I can just delete the examples, and all is well. Not a high priority problem. It does raise the question though, why would that be required? Can that initial import be a scoped
page.module.css
to avoid having to remove docs that are helpful to new developers in the future?To Reproduce
Interestingly, I can't reproduce using a basic stack blitz, even clicking through to Page and back to ComponentA doesn't have the effect. It's reliable on my local though.
System
Additional context
No response
The text was updated successfully, but these errors were encountered: