-
-
Notifications
You must be signed in to change notification settings - Fork 983
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
Unable to scroll to requested position, window.parentIframe not found #868
Comments
When your nesting iFrame, the one in the middle needs both JS files |
I have this problem, I have this iframe in a sotrybook and iframe-resizer thinks my parent iframe is an intermediate iframe because storybook itself works with iframes. I don't want to move the scroll to the topmost parent, just to my parent iframe. |
Not sure I fully follow the question. Do you want to scroll an intermediate iframe, but not I think I need to see a working demo to fully understand the issue. |
Yes that's it, I have something like this:
I just need my child to tell its first parent to move the scroll, the top iframe is not controlled by me and does not have iframe-resizer. In this case it is a storybook but the problem will arise for any site that will integrate my parent page. |
Just out of interest does |
No, I have the same error |
Just published |
Version |
Thanks for the feedback, I will get a final release out later this week. |
Released |
Hi @davidjbradshaw
I wonder if you could help me, I'm not sure if it's an issue or it's already that I'm doing something wrong with your plugin.
It gives me this error:
[Nested host page: eAppIframe] Unable to scroll to requested position, window.parentIFrame not found
I'm using your plugin inside my vue Application and this is the code where I think it fails:
App.vue
My code on the html above this component is this:
On
init
function I basically create global iFrameResize default values and a bit more, I'm going to omit with three points code that I think has nothing to do with it.init.js
Do you understand or have a hint about what's going on?
I've the feeling this way to load iframeResizer is not giving enough time to the parentIframe to be loaded. App.vue loads iframeResizer later than init.js configures everything and that leads to spam out that issue...
Thank you very much for your attention!
The text was updated successfully, but these errors were encountered: