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.
Hello, Jean-Guy Boulay. We haven't seen this problem on our side, so I'm glad you reached out.
We'd love to see those private review links that compare the two publishes. You can send those our way by clicking here. We'll have a look and let you know what we find!
Sure thing Alyssa, case number 01778082 submitted. I confirmed that this is indeed causing a scaling problem by reverting back to the earlier build and then republishing. The previous build definitely scales properly.
Hi again, Jean-Guy. I checked in on your case, and it looks like Renz logged this as a software bug. As soon as we get this resolved, we'll send you an update. Thanks for bringing this to our attention!
I hear your frustration, and I'm going to update our team on this bug's continuing impact. The second there's more information to share; this discussion will be the first to get notified. Thanks for bearing with us.
Thanks for this. I am following as I am working on a large project with embedded objects for an interaction. I feel like downgrading to SL2 from 360 when you are working on a solution is a gamble for my project. Keeping myself posted.
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.
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?
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.
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.
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.
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)
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?
30 Replies
Hello, Jean-Guy Boulay. We haven't seen this problem on our side, so I'm glad you reached out.
We'd love to see those private review links that compare the two publishes. You can send those our way by clicking here. We'll have a look and let you know what we find!
Sure thing Alyssa, case number 01778082 submitted. I confirmed that this is indeed causing a scaling problem by reverting back to the earlier build and then republishing. The previous build definitely scales properly.
That's helpful to know, Jean-Guy. I'll share that with Renz.
I see he recently requested your project file for testing – let me know if you have any trouble sending your file to us!
File shared, look forward to hearing back. Thanks
Hi again, Jean-Guy. I checked in on your case, and it looks like Renz logged this as a software bug. As soon as we get this resolved, we'll send you an update. Thanks for bringing this to our attention!
Hi Alyssa,
+1 on this - we're seeing the same thing with our web object publishes too; they're not scaling properly in the browser.
Confirmed, Still an issue in the latest build 3.27. Only works correctly in 3.25.
Hi Aidan,
Thanks for letting us know that you have run into this issue as well.
This conversation is attached so that we can share updates with you here.
It looks like Jean-Guy shared our current known workaround and you can find the details of how to install a previous version here.
Hi!
Do you know when this problem will be solved?
Thanks,
I know right? All these great new features being added to Storyline yet we can't upgrade because Web Objects are gimped.
Hi, everyone!
I hear your frustration, and I'm going to update our team on this bug's continuing impact. The second there's more information to share; this discussion will be the first to get notified. Thanks for bearing with us.
Thanks for this. I am following as I am working on a large project with embedded objects for an interaction. I feel like downgrading to SL2 from 360 when you are working on a solution is a gamble for my project. Keeping myself posted.
Just checked and it looks like it's still an issue in version 3.31
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.
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.
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.
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.
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.
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?
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.
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.html
Storyline 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.html
Source Files:
http://www.crssec.com/client/abw123/story%20and%20published%20files.zip
Note that I tried Modern and Classic (with scaling) players and the results are the same.
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.