I thought I posted this early but now I do not see it. Attached are screenshots of the same web object, one published using the April 26th update (webobject broken.jpg) and the other with March 21 version of Storyline (webobject working.jpg. Basically it is no longer responding to the browser size changing. I had to revert to April 26th release to get it sizing properly again.
Hi there, Curtis. We've discovered an issue where web objects aren't displaying correctly with the modern player in update 26 of Storyline 360. I'm sorry you're being affected!
I'll make sure this discussion is updated with any changes. It sounds like rolling back to the previous update (February 26) is working for you now, but please let me know if you are hitting any roadblocks.
This is still not fixed. I have to stay on the Feb 26 released. Web objects no longer scale with the stage. Our Storyline stage size is 1618x1014 we create web objects at that size and they normally resize with the stage.
So sorry you're still dealing with this bug, Curtis. We've got our eyes on it, and we'll update you as soon as we know more. You're in the right place!
If you look at the screen shots above, you can see what is happening. I had to quickly revert back to the version of Storyline before the issue started. Basically our web objects are no longer responsive after the April 26th release.
Okay I got two examples up. Both the exact same web object, same slide. One using Feb 26 version of Storyline and one with the release put out today, June 18th.
I know that a change in Storyline has caused this issue, but a solution may lie in the authoring tool you used to create the svg animation. I played around with the animation variables some, but was not able to get it to resize dynamically with the browser window. May I ask what app you used to create the animation?
It is all hand coded html. I use the Greensock tweening engine for the animation part. I thought about changing the stage size to a percentage but I do not think that will fix it.
You might try that and see what happens. I've attached a screen recording of the VideoJS player inserted into 360 as a web object. You can see that it scales very well with the rest of the project. The video tag used to insert it has an attribute of height="100%". Below is the CSS used to style the page.
37 Replies
Hi there, Curtis. We've discovered an issue where web objects aren't displaying correctly with the modern player in update 26 of Storyline 360. I'm sorry you're being affected!
I'll make sure this discussion is updated with any changes. It sounds like rolling back to the previous update (February 26) is working for you now, but please let me know if you are hitting any roadblocks.
Rolling back worked fine for me. Thanks for the response!
This is still not fixed. I have to stay on the Feb 26 released. Web objects no longer scale with the stage. Our Storyline stage size is 1618x1014 we create web objects at that size and they normally resize with the stage.
So sorry you're still dealing with this bug, Curtis. We've got our eyes on it, and we'll update you as soon as we know more. You're in the right place!
Thanks Alyssa!
Any chance this is resolved with the May 28 release? :) I do not see anything in the release notes.
Hi Curtis,
No update at this time. This conversation is linked to the report so that we can share updates with you here.
:( thanks!
Curtis, can you attach a sample slide that shows this issue?
If you look at the screen shots above, you can see what is happening. I had to quickly revert back to the version of Storyline before the issue started. Basically our web objects are no longer responsive after the April 26th release.
Is this happening only on mobile devices?
No, it happens everywhere. I if I have time this week I will update publish and then revert again.
That's why I wanted to see a sample file from you, I can't replicate this on the desktop.
My understanding was that this is known bug, is that not the case? I should have some time today to get a working example up.
Maybe it appears only under certain circumstances. I'm thinking if it was widespread, a lot more people would have jumped onto this thread.
Agreed, I was surprised more people have not brought this up.
It was brought up here too https://community.articulate.com/discussions/articulate-storyline/web-object-size-problem-with-last-360-update
Ok. If I can see a specific example, I might be able to find a workaround for the issue.
Okay I got two examples up. Both the exact same web object, same slide. One using Feb 26 version of Storyline and one with the release put out today, June 18th.
This does not scale beyond its size 1618x1014, which is our stage size
Today's release: https://360.articulate.com/review/content/1e2946e5-e84f-4e76-ba0f-7fc91372415c/review
This does scale both when you expand the browser window and when you shrink it.
Feb 26th https://360.articulate.com/review/content/6cfc163a-169e-47af-8b22-1c0b065e83e4/review
We make everything for Chrome BTW. Our entire user base is on Chrome.
Can you share this one slide in a .story file?
Here it is. This taken out of our template
I know that a change in Storyline has caused this issue, but a solution may lie in the authoring tool you used to create the svg animation. I played around with the animation variables some, but was not able to get it to resize dynamically with the browser window. May I ask what app you used to create the animation?
Let me clarify my last comment: Even outside of Storyline, your index.html file does not resize with the browser window.
It is all hand coded html. I use the Greensock tweening engine for the animation part. I thought about changing the stage size to a percentage but I do not think that will fix it.
You might try that and see what happens. I've attached a screen recording of the VideoJS player inserted into 360 as a web object. You can see that it scales very well with the rest of the project. The video tag used to insert it has an attribute of height="100%". Below is the CSS used to style the page.
This discussion is closed. You can start a new discussion or contact Articulate Support.