Scroll panel on feedback layer (modal fence) in HTML5

Apr 03, 2014

Hi all, this is my first post. Recently I found myself sitting at a table with Tom Kuhlmann and David Anderson at the iDesignX conference in Sydney ( ! ) which was pretty cool. I've been meaning to start being more active in the eLearning community in general, and this seems like as good a place as any to start...

Anyway, we had this issue and couldn't find anything on it (sorry if that was due to my search skills).

The problem is the scroll panel not working on feedback layers. One solution is to add 'visibility: hidden' to .modalfence in player.css

Just curious if anyone else has come across this issue and how they got around it.

Cheers!

6 Replies
Ashley Terwilliger-Pollard

Hi Grover and welcome to Heroes! 

I checked and there is an existing issue with our QA team right now where the scrolling doesn't work correctly in feedback layers while viewing the HTML5 content. I'll add your thread and potential workaround to that report, and in the meantime I'd suggest to continue using that workaround. 

Can you also confirm which update of Storyline you're using?

Robert Lengacher

Grover, Thanks for this tip! We just discovered this issue in SL2 published HTML5 content, which is likely affecting the hundreds of modules we have published in recent years. I just edited the player.css file for a published module, and the scrolling panels are now working. I'm following up with Articulate support to see if applying this fix is likely to have any unintended consequences. If not, then I'll work with my organization to see if we can run a script on all of our published content to get it fixed.

Ashley Terwilliger-Pollard

Hi Robert,

I see that Renato was able to test your file and confirmed the behavior with the scrolling panel and that it's been reported to our QA team for additional investigation. Also, I see you both discussed an alternative to the behavior that was a modification of the published output so you're welcome to use that with caution. 

This discussion is closed. You can start a new discussion or contact Articulate Support.