SL2 HTML5 Menu in Lightbox error
Nov 11, 2014
By
Phil Eagles
Hi,
I have created a custom menu in SL2. The menu is opened via a lightbox and the menu is contained within a Scrolling Panel. The menu works fine as Flash output but on HTML5 output it only works within the visible scrolling region. i.e. if you scroll to the bottom of menu it no longer goes to the correct page.
I have attached a link here: http://setup.proofing.brayleinolearning.co.uk/menuerror/story_html5.html
I have attached the Story file too.
9 Replies
Hi Phil!
I'm not sure that I'm fully understanding what you are reporting. Either that or I'm not seeing the same behavior.
Here is my published output: http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/stp196fvtgqb5uj1k5t1k51dck1ml04/story.html
Do you see the same behavior that you are reporting?
Hi, I'm still getting the same error as you. Open up the light box menu and scroll down to menu item 13 or higher and try selecting it. I cannot select any menu button below 12 i.e. when you use the scroll panel.
Also try using the html5 link http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/stp196fvtgqb5uj1k5t1k51dck1ml04/story_html5.html
Hi Phil
I get this behaviour - I can select buttons below 12 and it returns menu items out of order...if I select Menu Item 12 I get item 10, if I select item 14 I get item 12. I tried adjusting your story by adding hotspots to the text boxes but it does exactly the same thing.
Hi Wendy,
I experience exactly the same behaviour as you. I think what's happening is that the click action on the objects is staying in the same position despite moving the scroll window. Whilst it should be moving with the objects. Very strange behaviour and a definate bug I think.
Its not ideal but maybe you could
1. make the slide two columns wide to keep your menu items all on one slide that doesn't scroll, or
2. have a continue button on the menu slide so that it spans two slides - not ideal though...
hope it works out
Good workarounds, thanks for your suggestion. I'm hoping Articulate apply a fix for this ASAP as I won't have to compromise the design.
Hope so to...good luck
Hi Phil! Thank you for the additional information and thank you Wendy as well.
I have reported this issue to our QA Team for investigation.
I will post back here when applicable.
This discussion is closed. You can start a new discussion or contact Articulate Support.