It sounds like you may be running into a reported bug. Are you seeing this when viewing the HTML5 output in Chrome? That's what we have reported and I'd be happy to add this thread to the report as we track user impact.
I wanted to share some information on how we define bugs and how we tackle them when they occur.
Thanks for confirming Pam. I've added this thread to the report as we are currently tracking user impact and this will also allow us to update you here when we can.
Ok so this was over one year ago - has this been fixed yet? I have just stumbled across the same thing in SL 2. In Chrome the default start point for the drop down is the first option in the list of answers, rather than "-select-" and it just doesn't look right. I imagine since 360 is now mainstream that SL2 bugs get less attention. Is this going to be fixed at some point? (I use both SL2 and 360 so upgrading is not an option)
Hi there, Brian. You're right -- this issue is still open for Storyline 2 but fixed in Storyline 360. We aren't planning any new releases for Storyline 2, but we'll continue to watch for changes that break key functionality.
5 Replies
Hi Pam,
It sounds like you may be running into a reported bug. Are you seeing this when viewing the HTML5 output in Chrome? That's what we have reported and I'd be happy to add this thread to the report as we track user impact.
I wanted to share some information on how we define bugs and how we tackle them when they occur.
Hi Leslie
Yes this a Chrome issue. I have published the course to LMS with all HTML5 options selected.
Works fine in IE.
Where is this in the priority of bugs being fixed?
Pam
Thanks for confirming Pam. I've added this thread to the report as we are currently tracking user impact and this will also allow us to update you here when we can.
Ok so this was over one year ago - has this been fixed yet? I have just stumbled across the same thing in SL 2. In Chrome the default start point for the drop down is the first option in the list of answers, rather than "-select-" and it just doesn't look right. I imagine since 360 is now mainstream that SL2 bugs get less attention. Is this going to be fixed at some point? (I use both SL2 and 360 so upgrading is not an option)
Hi there, Brian. You're right -- this issue is still open for Storyline 2 but fixed in Storyline 360. We aren't planning any new releases for Storyline 2, but we'll continue to watch for changes that break key functionality.
This discussion is closed. You can start a new discussion or contact Articulate Support.