Forum Discussion
web objects no longer scale with the browser
Since this latest update the web objects are no longer scaling with the browser.
I can provide private review links to compare the two publishes upon request; one from latest SL update, and one from previous. Sorry can't share the tech demo with public.
30 Replies
- Jean-Guy-BoulayCommunity Member
Just checked and it looks like it's still an issue in version 3.31
- JamieCioCommunity Member
Thanks so much, Jean-Guy; I'm also monitoring this issue and hoping for a resolution.
So it sounds like following the instructions to install a previous version and going back to version 3.25 of Storyline 360 will work? Have you run into any problems with version 3.25?
Obviously that's not a good long-term solution, but we're running low on options if the engineering team isn't able to quickly locate and reverse the code change that caused this serious error.
- Jean-Guy-BoulayCommunity Member
Sorry for the late reply, I've been able to open v3.3x projects in 3.25, but you lose the ability to use the nice built in variables that Articulate added since v3.25. If your project hasn't taken advantage of them, then you shouldn't have any issues.
- JamieCioCommunity Member
Thanks, Jean-Guy! And yes, another vote to make sure 3.25 is easily available. Given that there are some compatibility issues for downgraders, that's another good reason for the engineering team to prioritize a proper fix.
- barbkochCommunity Member
We have been reverting to version 3.25 to resolve the issue. However I've found another issue: The drop down menu no longer lists the version of storyline that I need. Any ideas on how to get the previous version?
Hello Barb and welcome to E-Learning Heroes :)
Thanks for reaching out and sharing what you are running into with your software.
It sounds like you would be best suited to work directly with our support team on this and I've opened up a support case on your behalf.
You should be hearing from someone soon.
- Jean-Guy-BoulayCommunity Member
Yes Please re-enable the old install or even better just fix the scaling of the webobjects. It's like the support team is working against us.
- AndrewEngland-2Community Member
Hi Articulate. Any update on this serious issue?
We're finding this change in the way WebObjects are now scaling is causing many problems when maintaining older builds.
How can I access the older version 3.25 if it needed as a backup resolution to this?
- Jean-Guy-BoulayCommunity Member
Hey Andrew, I was able to find the 3.25 installer by looking at the articulate lnstall logs for it's location. This of course won't work if you cleaned your temp folders.
Hi Andrew,
I do not have an update at this time.
Within the software, you have access to the latest 7 versions that you can install.
Update 25 is prior to this, but you can reach out to our support team here if needed.
- AllanWeghorst-2Community Member
I just posted the same problem on this discussion: https://community.articulate.com/discussions/articulate-storyline/scaling-and-web-objects
The webobjects used to scale with the browser prior to version 3.26. But starting with version 3.26 in April webobjects no longer scale, and now get scrollbars when the browser is too small.
I created a very simple test to illustrate the problem, and am providing the source files.
Compare the same storyfile here published with versions 3.25 and 3.32 (and resize your browser to see the difference)
Storyline 3.25 HTML5 Output (the old scaling way):
http://www.crssec.com/client/abw123/SL_version3.25%20-%20webobjtest4%20-%20Storyline%20output/story_html5.htmlStoryline 3.32 HTML5 Output (new non-scaling and with scrollbars):
http://www.crssec.com/client/abw123/SL_version3.32%20-%20webobjtest4%20-%20Storyline%20output/story_html5.htmlSource Files:
http://www.crssec.com/client/abw123/story%20and%20published%20files.zipNote that I tried Modern and Classic (with scaling) players and the results are the same.
- JamieCioCommunity Member
Wow, on browsers like Safari where scrollbars are hidden by default, the problem is even worse; it's not necessarily even obvious that you need to scroll to see the content.
Any answers at all from the engineering team? Are they working to resolve this problem?
No update at this time, Jamie.
I wanted to share some information on how we define bugs and how we tackle them when they occur.
I'm sharing your subsequent thoughts with our team as we continue to dig in.
Related Content
- 12 months ago
- 7 months ago
- 10 years ago