Hi! I've been searching a bit and haven't found any discussion of this - The preview within Storyline 360 looks great, but is there a way to preview in a web browser? We have users with both Edge and Chrome and it would be helpful if there was a way to quickly check something in the actual browsers without having to publish the project.
If this has been discussed, please feel free to point me in that direction!
Echo to Ron's suggestion. I often publish to C:\Temp and then launch the *.html file in different browsers to get an idea of the behavior differences (if any).
I'll echo (echo... echo...) Ron & Joe: Publish for Web to your local drive, and test that.
BTW, I find this helpful for quality-assurance testing/editing. I step through the published version of the course. When I find something that needs correcting (e.g., typos!), I fix it immediately in the .story file. Then I keep stepping through the published version to ensure the entire thing works as expected. That includes stepping through it backwards, to check that PREV goes where it should, and slides behave as expected on revisiting. Depending on the number of complexity of corrections, I'll repeat that process.
Why? Because (I speak from experience here): some things that work when you preview a given slide don't work going forward or backward through the overall course.
4 Replies
The Publish to Web function would allow you to view a course locally in any browser you choose.
Thanks, I will check that out. I'm still new to Storyline so am learning the terminology and workflow.
Echo to Ron's suggestion. I often publish to C:\Temp and then launch the *.html file in different browsers to get an idea of the behavior differences (if any).
I'll echo (echo... echo...) Ron & Joe: Publish for Web to your local drive, and test that.
BTW, I find this helpful for quality-assurance testing/editing. I step through the published version of the course. When I find something that needs correcting (e.g., typos!), I fix it immediately in the .story file. Then I keep stepping through the published version to ensure the entire thing works as expected. That includes stepping through it backwards, to check that PREV goes where it should, and slides behave as expected on revisiting. Depending on the number of complexity of corrections, I'll repeat that process.
Why? Because (I speak from experience here): some things that work when you preview a given slide don't work going forward or backward through the overall course.