Forum Discussion
Odd Scrolling panel issue
I know there's been a few issues over time with scrolling panels jumping with a couple of solutions that have worked for people.
This one is a bit unusual. I have a scrolling panel with screenshots to replicate a clinical system. It has a hotspot within it that, if clicked, launches a layer to say they've not clicked in the right place. If they click that, then the scroll panel leaps back to the top. Not a deal breaker for this length of scroll panel, but annoying and it would be a deal breaker for longer scrolling pages.
The slightly weird bit is clicking on a button OUTSIDE the scroll panel also launches the incorrect layer, given certain conditions. This does NOT cause the scroll panel to jump back.
So, I then tried adding a trigger so that if the user clicks anywhere inside the scroll panel OUTSIDE of the correct parts of the elements within the scroll panel, that it would launch the error layer, and this does NOT cause the scroll panel to leap to the top. So, I have a workaround for now, but thought I'd flag the issue.
Out of interest I added a SHAPE inside the scroll panel to trigger the error layer, and this also DIDN'T cause the scroll panel to leap to the top. So it seemed to be that a hotspot inside a scroll panel launching a layer would cause the scroll panel to jump.
But, then to add to the weirdness, I've basically recreated this in simple form to share a file here, and the workarounds in this version DON'T work. Any clicks inside the scroll panel to launch a layer are causing the scroll panel to jump back up again.
I can't share my original to show workarounds working but I can share this simple example file to show the issue - nothing I've tried in this file works to stop it jumping back up.
1 Reply
Hi PeterGrennan! Thanks so much for sharing the file and walking us through what you found. That level of detail really helps! I ran some tests and saw the same thing: when a hotspot inside a scrolling panel opens a layer, the scroll panel jumps back to the top once you return to the base slide.
That’s the current expected behavior since Storyline reloads the base slide after closing a layer, but I totally get how that could be frustrating on longer scrolls. Your shape-trigger workaround is a smart one and will definitely help others who run into this.
I’ve shared this with our team so they can look into it, and we’ll update the thread if anything changes in the future. Really appreciate you flagging it so clearly.
Related Content
- 5 months ago
- 2 months ago
- 8 months ago