176 Replies
Justin Grenier

Hey again, Cathy.

I get an error when I hit the Evernote link you shared, but it sounds like Vimeo's finding is perfectly consistent with the screencast that I shared here.  Yes, Storyline is placing Vimeo's IFrame player inside another frame, just as it always has.  I'm not sure what changed at Vimeo that caused them to no longer like this model, but we at Articulate have not made a change here.

Cathy DeBurro

More information from Vimeo

It’s not looking good, folks. ☹

Hi Cathy,

Again, my sincere apologies for this inconvenience. To provide a brief overview of how this occurred:

1. In the past, fallback options in the browser allowed some version of fullscreen to operate even when within frames.

2. Within the last few weeks, updates to major browsers removed these fallback options. This caused the fullscreen button to fail when clicked. Vimeo videos would no longer enter fullscreen if they were placed within frames.

3. Because the button wouldn’t work anyway, in the last few days our developers have now removed the fullscreen button from any players that are embedded within frames. To confirm, the button would have been broken even if displayed. So, whether the button was there or not, your viewers would not be able to enter fullscreen.

So, like I said, no action you took caused this to occur. However, your site appears to have been created in such a way that will not allow full-screen Vimeo embeds.

I’m sorry I don’t have a better answer for you. Please write me back for any further questions.

Cathy DeBurro


Ironically - that's what Vimeo is asking too:

Hi Cathy,

I am very sorry, but as long as your embeds are placed within frames, they will not display the fullscreen button.

Have you inquired with your web developers about this issue? They may be able to propose a solution that is not available to me. I

am limited to advising on Vimeo's functionality, and they may be aware of a work-around that I do not know about.
Hoping that Articulate can propose a solution. :)
The information contained in this message is proprietary to the sender, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.

Ashley Terwilliger-Pollard

Hi Bryan,

We shared the information here with our QA team for additional review, but I don't have any information to share yet in regards to if there is a change we can make in terms of how the Vimeo videos are embedded within our iFrame. Once we have information to share we'll update the thread and as long as you stay subscribed to the thread you'll receive a notification via email. In the meantime, you won't be able to use the Vimeo full screen button within the Storyline or Studio output. 

Cathy DeBurro


Thanks again for your help here. I spoke with my management about this issue and our first choice option is to stick with Articulate Storyline. However, we absolutely require full screen capability from embedded videos, because the videos are code based training demonstrations and they are viewed globally, including low bandwidth countries.

If this can be resolved through Storyline architecture, then I will need you to provide a timeframe for this update that I can provide to my management. If this can't be resolved, or the timeframe is too long, we will need to find another solution.
I am keeping my fingers crossed that you will be able to make the modifications needed in relatively short order! Thanks!


Justin Grenier

Hey Cathy,

As much as I'd love to be able to to help, we won't be able to commit to a fix for this issue in the short term.  We will evaluate and prioritize Vimeo's change according to its breadth and depth of impact on our customers and make a decision from there, and we'll keep this forum thread updated with any developments.

In the interim, if you find a product or service that is handling Vimeo's update better than we are, we'd welcome that information as well.

Good luck with your project!

Cathy DeBurro

Completely understand. I will start the research project…and I will certainly pass anything that I uncover over to you….but the point here is that if ‘frames’ are considered legacy by the major browsers, then that will impact your architecture, which is why we need to consider switching. Not because of Vimeo – but because the 3 major browsers are stopping their support of it. That’s the issue. ☹


Justin Grenier

One minor point of clarification, Cathy.

Vimeo does not seem to be stating that IFrames are legacy constructs.  In fact, the IFrame tag is very much a part of the HTML5 standard and continues to be supported by all major browsers.  Vimeo seems to be stating that browsers no longer allow full-screen functionality to be implemented within an IFrame.  I can't confirm the accuracy of that statement, but I'm sure Vimeo knows their stuff.

This is a subtle difference and is of little help to you, but it illustrates the difficulty of a fix, since IFrames are used (and will continue to be used) extensively throughout Internet architecture.

...and for what it's worth, I can't seem to make Vimeo videos play full-screen in Adobe Captivate, Lectora Inspire, or iSpring Presenter either, though I'm no expert in any of those tools.

Cathy DeBurro


Thanks...much appreciated.  A question - do you know if people using YouTube are having this same difficulty?  Personally - I would much rather stay with Articulate than move to another solution....so finding a resolution to embedded video 'full screen' capability - if outside of Vimeo is certainly an option that we are open to. :) 

Cathy DeBurro

Bummer.  Unfortunately neither ideas are valid for us.  Many of the testers who use our products are in low bandwidth countries -- where they can't handle trying to open / stream the file from our servers.  The embed method is the only option there.  And, because they are embedded inside of courses taken within an LMS environment, we don't want users to have to go outside of the environment to watch the videos-- it's not a great user experience to do that. :(

We will keep digging....thanks!

Stuart Norris

Ok here we go, i've just shared my thoughts and the screencast posted above and had a response from the Vimeo team to clarify the problem. Here's a link, I would be grateful to see where Articulate stand on this issue after receiving this feedback...


or check out this attachment of my response. It alarms me that neither party seem particularly keen to resolve this issue. This potentially has a huge impact for a large portion of our client base and i would be grateful for some clarification on this issue.