Based on your screenshots this should work without issues. I would delete and recreate the trigger, just to be sure. Also, see attached a quick test that works for me in both Preview and when published.
Oh, you are using HTML5. Hover doesn't seem to work (see here the HTML5 version of my hosted testfile) in HTML5, although Articulate lists it as supported.
Would you be able to share the .story file you are having difficulty with Christopher so that we can take a look? Just let me know what slide to take a look at.
Actually, it's proprietary, so I can't share the file. However, I think I found another piece of the puzzle.
I saw another article which explains why regular HTML might not open (due to the Flash Player) and how to correct it. When I test the mouseover functionality, it works just fine in regular HTML. It does not work in HTML5.
Do you know what's different in HTML5 that prevents this trigger from working?
Hey there, Christopher. I'm checking out this issue, as I could see exactly what you're describing with Michael's test file in my HTML5 browser environment. Thanks for bringing it up.
To note, and it sounds like you figured this out, you'll want to be sure to test your content in its intended environment (uploaded to a web server) rather than opening the published file locally on your machine. Browser security settings at the local level might prevent certain features of your course from functioning.
I'm able to reproduce this behavior in a new file: Here's my HTML5 output for you to test as well. I wanted to be sure there wasn't a larger issue, so I tested the following scenarios:
Hyperlink in a text box to jump to URL: works as expected
Trigger to jump to URL on a shape: works as expected
Trigger to show a layer when hovering over text box: works as expected
Hyperlink in a text box to show layer: doesn't work
I'll create a report for our QA team to investigate this behavior since it is not consistent with the Flash (HTML) output. We will update this discussion when we have new information to share.
As a possible workaround, are you able to use a hotspot over your hyperlink text and use a mouse-over trigger on the hotspot to show the layer?
Hi, is there an update on this bug please? I have a hyperlink in a scrolling text box that will not show the layer. I cannot use a hotspot for this scenario.
This bug is still open in Storyline 2, but it was fixed in Storyline 3 and Storyline 360. What version of Storyline are you using? If you're using SL3/360 and still running into this issue can you make sure you're on the latest update?
16 Replies
This post was removed by the author
Based on your screenshots this should work without issues. I would delete and recreate the trigger, just to be sure. Also, see attached a quick test that works for me in both Preview and when published.
Interesting. I tried Michael Hinze's example and it did the same as mine; it worked in preview, but not published.
Could this be a firewall/security software issue on my system?
Hi Christopher
are you viewing the HTML or html5 published output?
SL2 previews in flash
Here is a link to the published version running off my server. Give it a try and see if that works for you.
I have been using the html5 link. I haven't been able to get the HTML link to open.
Oh, you are using HTML5. Hover doesn't seem to work (see here the HTML5 version of my hosted testfile) in HTML5, although Articulate lists it as supported.
I followed the steps on articulate to fix the Flash player issue, so now I can open regular HTML files rather than HTML5.
However, the link text still won't work in regular HTML. I get a cursor change where it recognizes the link, but the hidden layer doesn't show.
Is there some other setting I'm missing?
Would you be able to share the .story file you are having difficulty with Christopher so that we can take a look? Just let me know what slide to take a look at.
Actually, it's proprietary, so I can't share the file. However, I think I found another piece of the puzzle.
I saw another article which explains why regular HTML might not open (due to the Flash Player) and how to correct it. When I test the mouseover functionality, it works just fine in regular HTML. It does not work in HTML5.
Do you know what's different in HTML5 that prevents this trigger from working?
Hey there, Christopher. I'm checking out this issue, as I could see exactly what you're describing with Michael's test file in my HTML5 browser environment. Thanks for bringing it up.
To note, and it sounds like you figured this out, you'll want to be sure to test your content in its intended environment (uploaded to a web server) rather than opening the published file locally on your machine. Browser security settings at the local level might prevent certain features of your course from functioning.
I'll post my findings here as soon as I can!
I'm able to reproduce this behavior in a new file: Here's my HTML5 output for you to test as well. I wanted to be sure there wasn't a larger issue, so I tested the following scenarios:
I'll create a report for our QA team to investigate this behavior since it is not consistent with the Flash (HTML) output. We will update this discussion when we have new information to share.
As a possible workaround, are you able to use a hotspot over your hyperlink text and use a mouse-over trigger on the hotspot to show the layer?
That is how I wound up fixing it. The hotspot works just fine in either format. I'm glad that's available as a back up.
Thanks for your help.
Oh good; I'm glad that was an option for you, too.
Hi, is there an update on this bug please? I have a hyperlink in a scrolling text box that will not show the layer. I cannot use a hotspot for this scenario.
Hi Simon and welcome to E-Learning Heroes :)
What version of Storyline are you using? We have this marked as corrected in Update 12 of Storyline 360.
Hi Simon,
This bug is still open in Storyline 2, but it was fixed in Storyline 3 and Storyline 360. What version of Storyline are you using? If you're using SL3/360 and still running into this issue can you make sure you're on the latest update?
This discussion is closed. You can start a new discussion or contact Articulate Support.