Forum Discussion
Hyperlink hover effect on text that breaks over lines
When I create a hyperlink that breaks over more than one line using the Hyperlink feature it only activates the hover effect over one line per time rather than over the whole string of text. Can someone help me with this problem?
Hello Everyone!
I wanted to share some good news! We are no longer seeing the bug where a hyperlink line extends past the characters if the linked text reaches a line break (Storyline version 3.72.29699.0).
To confirm or update your version of Storyline:
- Launch the Articulate 360 desktop app on your Windows machine.
- Click the drop-down arrow next to Storyline 360 and select Other Versions.
- Here you will see the current version being used, or have the option to update.
Please let us know if you're still encountering the issue and we'd be happy to continue troubleshooting with you in a support case.
38 Replies
So sorry this is still plaguing you, Karen! We're still seeing this issue in Storyline 3. As soon as it's resolved, we'll share the news here!
I'm having this issue in 360 and have a client who is NOT happy about it as there are multiple links in a very short course. Any update on this?
Still broken, I had to overlay hotspots in one course, in another I created hover states in individual textboxes
Ug. Ok, thanks for the workaround suggestions.
Is there an update on this issue, I am having the same problem.
This is fixed in 360 I believe
Hi Samantha,
I do not have an update on this issue and it is still open with our team.
This conversation is attached so that we can share any updates and you should now be subscribed as well.
Hi everyone!
I see there is some confusion with this bug! It is fixed in Storyline 360 Update 36 (Build 3.36.21213.0). If you are still hitting this snag and on an older version of Storyline 360, we recommend updating your Articulate 360 desktop app.
hi, I have version 3.37.21453.0 installed and this bug is still in existence.
Hi Karen!
Thanks for returning with an update! Unfortunately, I was able to recreate this bug as well in Storyline 360 Update 37 (Build 3.37.21453.0). I've added your comments to our active report.
I'll report back to this discussion when I have an update!
