-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Uncaught DOMException: Blocked a frame with origin "http://localhost:9009" from accessing a cross-origin frame. #7215
Comments
This is still not resolved; should we re-open this or open a new issue? |
Clicked actions like in the documentation are working in Chrome but not in firefox. <Button onClick={action("clicked")} disabled={boolean('disabled', false)}>
{text("Children (text)", "Hello World")}
</Button> Click the button above logs the event details in chrome but not in FireFox. |
… occurs, we catch it and can proceed storybookjs/storybook#7215
I opened a fix PR in telejson! |
Crikey!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.3.0-beta.8 containing PR #8940 that references this issue. Upgrade today to try it out! You can find this prerelease on the Closing this issue. Please re-open if you think there's still more to do. |
|
@zeorin could you check to see if the |
@ndelangen it is for me:
|
Thank you for checking. Will put this back on my todo list |
Head slap! Yes - that is it. For clarity, this works just fine:
|
@shilman is that known? I ask because that was not always the case before v6, you could easily build an instance, compress it and share it with others. I feel like it's possible that a lot of people in this thread are running into this because it's not being run on a local server for whatever reason. |
@reywright This issue is still open, isn't it? 😉 I think we were looking for a repro and the repro is to open built storybook from a file URL @ndelangen |
I am also seeing this when trying to use Storybook Composition. It works fine within the original storybook, but I get the same error ( Anyone have ideas for a solution or workaround? EDIT: After further research I've tracked it down to a few specific stories. This error appears when storybook tries to serialize a |
I'm also having this issue. Our current workaround which worked is to disable the actions addon. |
As @anicholls mentioned edit. Same for me. I fixed this issue when i disabled docs addon all stories. |
Another update: I think I've tracked down the problem with the Docs addon and I've opened a separate issue for it here: #13608. Unfortunately the args (and their defaults) are extracted for all stories regardless of which ones have docs disabled so the only option to get composition to work is to disable the docs addon entirely. |
I solved this by opening storybook in an incognito window. It's possible that Chrome plugins are messing with the browser. |
I think we can close this issue now, #13608 was the fix. |
I am still seeing this issue having a similar case to @itsderek23. I recently upgrade storybook from What works?
What does NOT work (i.e. storybook page not rendered)?
Both cases above throw the following errors in the console.
I also have the docs addon disabled so I'm not sure how #7215 (comment) is the fix to this issue. Am I missing something here? |
I'd also like to link a similar case here with GitHub Pages storybook-eol/storybook-deployer#97 |
After removing |
I was having this issue and it turned out one of my Firefox extensions (Surfingkeys) was triggering it to happen. The question is why does this happen? |
In the case of I'm not sure if this is the same cause for |
Describe the bug
After updated storybook 3 to 5 the 'actions addon' throws CORS error when an action is performed. Figured out that setting the 'depth' option to 2 or less is a work around and no error appears. Posting bug report hoping any better solution may be found.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Actions should be performed.
Screenshots
N/A
Code snippets
I traced the bug to the following line:
This configuration fixes the issue. But it would be great to have this resolved and allow for display of action with greater depth of the object.
System:
Additional context
This happened after upgrading from 3 to 5. Default webpack config is used. Babel was also upgraded to 7.
The text was updated successfully, but these errors were encountered: