Forum Discussion
Storyline 3 not honoring Resize browser to fill screen
It seems that Storyline 3 does not follow the Player | Other | Browser Settings as it did in Storyline 2:
I expected the browser window to maximize and then the player to fill the browser window. Instead, I saw the browser size to the course dimensions.
My first thought that it was a 16:9 ratio but 4:3 produced the same result. The browser window opens to accommodate the player but then it never re-sizes the window to fill the screen. It is possible for the end user to maximize the window but this wasn't necessary when publishing in Storyline 2.
Here is what I'm seeing:
Same results in Chrome - the course does not maximize the window.
I then checked the publish settings to see if this was an issue for both Chrome and Internet Explorer:
HTML5 - Does not work
HTML5 / Flash - Does not work
Flash / HTML5 - WORKS!
Flash - WORKS!
I'm not sure if this is a HTML5 issue or not but I wanted to pass along my findings if others encountered this as well. It seems that if the publishing preference is for Flash then the resizing of the window will be honored as expected.
Thanks Ashley,
I'm curious as to why Articulate would take a feature that works in SL2 (browser size options) and remove it from SL3.
Hey Thor!
You're entirely right, browser size options aren't supported in HTML5 for Storyline 3 as you'll see noted here in the Player: Other section. That chart is a super handy reference for what to expect in each output.
As you've mentioned, pushing the Flash output will be the way to go to take advantage of this feature.
Hope that's helpful! Let me know if you have any questions 😊
I'm experiencing the same problem in addition to a captioning problem in Flash. I've been told that the captioning problem (showing ascii code for some characters) has been fixed in 360 and a fix is on the way for SL3. Will the resizing problem also be fixed with the next patch?
Both issues together are preventing me from publishing for either Flash or HTML 5!
Hi Diane,
The browser size options aren't in the HTML5 output, as noted in the comparison chart too. That is something that would be a feature request for Storyline 3 and Storyline 360.
For the ASCII code you mentioned, any fixes that you see within the current release of Storyline 360 will be included in the next update to Storyline 3. Take a look at the release notes here for a full list.
Hi Diane,
Those settings are the same across the two versions. Here is the SL2 comparison chart as well.
The settings are the same but they function differently, as is "articulated" in this thread. Why did the functionality change?
.
Hi Diane,
Are you changing the publish options as the original author mentioned as well?
The default for Storyline 2 is Flash first and you can opt-in to include HTML5 as well, so think of this as the same as Flash first/HTML 5 in Storyline 3.
If you are publishing the content with HTML5 only or HTML5 first/Flash fallback, then the behavior may be different in the browser.
Yes, I am. I've experimented with all 4 and had the same results as the original author.
It would seem logical, that if Flash is eventually going away, we would want to publish for HTML5 first. But that causes problems with browser size...as does publishing for HTML5 alone. This is the problem that needs fixing.
.
I understand Diane. You can read what we're doing about Flash here as we are aware and working towards that.
Hi Leslie, I came up with this limitation in a project. Do Articulate have plans to include this feature for HTML? Thanks.
Hi Eduardo,
What feature are you looking for?
Storyline 3 and Articulate 360 all have an option to publish for HTML5 first/only.
The browser size options aren't in the HTML5 output, as noted in the comparison chart too. That is something that would still be a feature request.I am experiencing a browser window resize issue with Storyline 360 when publishing a Flash/Html5 course. This only happens in the up to date version of Internet Explorer. Does this issue plan to be addressed by Storyline's development team or due to the impending demise of Internet Explorer and Flash, will this be a low priority issue for the development team?
Hi Doug,
Thanks for reaching out. I tested a course that I have on hand and it seems to be working as expected.
Can you take a look at my published output here?
I tested in both Edge and IE11 as I wasn't sure by what you meant with the 'up to date version' :)
