Forum Discussion
Trouble with hyperlinks in animated bullet points
For some reason, the hover/visited states of the hyperlinks in my project are not working consistently. For example, I've got different hyperlinks inserted into a single textbox with bullet points ...
Hello Everyone!
I'm happy to share that we have released Storyline 360 version 76 (Build 3.76.30446.0)!
Included in this release is the fix for the bug where Hyperlinks inside the same text box behave differently from each other when entrance animation by paragraph is applied.
Now all you need to do is update Storyline 360 in your Articulate 360 desktop app on your computer. You'll find our step-by-step instructions here.
Please let us know if you have any questions by reaching out to our Support Engineers directly.
Have a great day!
Sure, Kelly. I attached a test file. I created a set of links in a paragraph, duplicated the set, and added Animate By Paragraph to the second set.
You'll see the third link in the second set doesn't have the proper rollover/visited states. (In our testing, we've found it's typically the last or second-to-last link that breaks). Edit: Upon saving/closing and re-testing the file, it's now the second link in the second set that doesn't work.
There's another issue as well. The links are intertwined. Visiting a link in the first set changes the link in the second set to visited. We've found this happens even when changing the destination of the link, or even deleting the contents and making new links from scratch. The first link is still tied to the visited state of the original copy of the textbox, the second to the second, etc.
Hello Renee,
I'm really sorry to hear that you ran into this issue. I tested your project file and can confirm that I was able to observe the issue with the hyperlinks using the latest version of Storyline 360. I went ahead and filed this as a bug so our product team can take a look at the behavior you encountered, as well as the previous bug that was opened for this behavior. We'll be sure to leave a message here once we have new updates to share, and our apologies for any inconvenience this bug may have caused.
