Storyline 2 Web Object issues
Mar 06, 2015
1) In Google Chrome, if I have a Web Object on a slide in the Flash version (and a project set to scale to fill browser window), the Flash content does a weird stretch/stretch back when the slide is first navigated to. This makes the overall master slide design look a lot less seamless if the content keeps adjusting for a split second when entering a frame with a Web Object. Can anything be done about this? It seems like a bug to me.
2) When I have multiple Web Objects on multiple slides, it used to be (in Storyline 1) that only one would be output in WebObjects directory if all the Web Objects pointed to the same directory. But now, in Storyline 2, every time I include a Web Object, even if it is copy/pasted from another slide, another directory is added in the WebObjects output. This leads to a lot of unnecessary loading when going through a course, especially if the Web Object has a bunch of graphics/content. I prefer the way it used to work since it would only have to load once and then could just grab from the cache. Is there any way this could be fixed going forward?
Thanks.
2 Replies
Hi Keith,
Are you able to share an example file of the issue you've mentioned in #1 so that we could take a look at how you set this up and the behavior that is occurring.
In regards to the issue in #2, I know that Storyline 2 changed some of the ways in which files were package and published - so I don't know that there is any way to change this, but you're welcome to share your thoughts in the form of a feature request here.
Here is a .story file for the #1 issue. I didn't change much in this, just added a border to the slide master, a web object on pages 2 and 3, and changed the Storyline player to scale to fit browser window. When I publish and view this in Chrome on a web server, the scaling of the whole flash object (storyline frame) 'jumps' slightly when I first view slides 2 and 3. It doesn't do it again if i branch back from page 3, but if I reload the story.html I can see the issue again. It only happens in Chrome.
This discussion is closed. You can start a new discussion or contact Articulate Support.