Cannot get /iframe.html
See original GitHub issueDescribe the bug
I’m currently running into this issue when I run storybook locally. Storybook loads but I see the message Cannot GET /iframe.html in the window where the component should render.
Request URL: http://localhost:9009/iframe.html?id=*
Request Method: GET
Status Code: 404 Not Found
Remote Address: [::1]:9009
Referrer Policy: no-referrer-when-downgrade
Packages I’m using
"@storybook/addon-actions": "5.0.1",
"@storybook/addon-links": "5.0.1",
"@storybook/addons": "5.0.1",
"@storybook/react": "5.1.0-alpha.2"
Issue Analytics
- State:
- Created 5 years ago
- Reactions:31
- Comments:16 (6 by maintainers)
Top Results From Across the Web
Cannot get content of iframe - Stack Overflow
As you can see, the content of the iframe disappears when I try to get the document. What am I doing wrong? javascript...
Read more >JavaScript Cannot Get Elements From an iFrame
1. Establish a new JavaScript function designed to retrieve elements from an iFrame. · 2. Retrieve the iFrame and store it in a...
Read more >Javascript outside an iframe cannot access iframe properties ...
This shows that any line of JavaScript, even if only accesses the height of iframe element itself, is stopped from executing by the...
Read more >How To Get an Element in an iframe - W3Schools
How TO - Get Iframe Elements. Get an element from within an iframe with JavaScript.
Read more >HTMLIFrameElement.contentWindow - Web APIs | MDN
You can use this Window object to access the iframe's document and its internal DOM. This attribute is read-only, but its properties can...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I ran into this issue as well after migrating from extend mode to full control mode. Fixed it by changing the
config.pluginsoption fromto
It may be worth updating the docs at https://storybook.js.org/docs/configurations/custom-webpack-config/#full-control-mode to preserve the
pluginsconfig array as well@yairEO @lauterry Yeah well, you’re both REMOVING all webpack plugins, including the HtmlWebpackplugin, so it would make sense for there to be no html outputted.