Hi everyone! When I insert an iframe into a Wordpress post using the Plugin "Insert or Embed Articulate Content into Wordpress" the page will automatically scroll down to the iframe when loading that page. Is there a way to prevent this from happening either through:
1. insert some shortcode into this: [iframe_loader type='iframe' width='100%' height='425' frameborder='0' src='http://title/story.html']
This results from a browser conflict with code that allows keyboard commands to function as soon as a page loads. You may want to review the following options to avoid this behavior.
Ah, your reply was so helpful! I'll try modifying the published output and understand that this isn't supported. But in case you know... if I do this, will it solve the problem in some browsers while create new problems in other browsers?
I can't expect a reply, so let me just say my thanks to your team for having a really clear acknowledgement of the issue and well spelled out suggestions on how to solve it. Thanks so much!
I'm glad that helped, as I don't know the answer to your other question. I'd say to test in as many browsers as possible that your users may be utilizing to get a sense of how it'll work and then if there is a particular browser that you'd recommend they don't use - it would be best to share that info with them.
3 Replies
Hi Gardner,
I don't know specifics about that Wordpress plug in, but if you use an iFrame to embed a published Articulate Storyline course into a web page, you may find that the web page automatically scrolls down to the iFrame when it's viewed in Internet Explorer or Firefox.
This results from a browser conflict with code that allows keyboard commands to function as soon as a page loads. You may want to review the following options to avoid this behavior.
Ah, your reply was so helpful! I'll try modifying the published output and understand that this isn't supported. But in case you know... if I do this, will it solve the problem in some browsers while create new problems in other browsers?
I can't expect a reply, so let me just say my thanks to your team for having a really clear acknowledgement of the issue and well spelled out suggestions on how to solve it. Thanks so much!
Hi Gardner,
I'm glad that helped, as I don't know the answer to your other question. I'd say to test in as many browsers as possible that your users may be utilizing to get a sense of how it'll work and then if there is a particular browser that you'd recommend they don't use - it would be best to share that info with them.
This discussion is closed. You can start a new discussion or contact Articulate Support.