Forum Discussion
Unwanted scrolling of Storyline box in Rise
Hi
When the user clicks on the Storyline block in Rise that is not fully visible, the block auto scrolls. So much so that the new layer is not visible.
I'm wondering if anyone else is experiencing this and whether there is a way of structuring my SL content in Rise so this doesn't happen.
See the attached short video.
At the moment I'm putting up with this and not trying to find workarounds, as I have lots of content to deliver!
It would be really helpful if there are any fixes to these issues that they were actually updated here by the Articulate team. If there have been any resolutions to this I can't see that in the chat. It all seems a bit cloak and dagger and not the helpful open and supportive forum it is supposed to be.
I would agree with that. This is a recurring issue for a lot of people, and it would be great to have it resolved. By the way, this issue doesn't happen if you use Firefox as a browser, which isn't that helpful as most people have now moved away from using Firefox.
Normally changing browser would be my first port of call with something like this. My organisation however, controls the default browser used when opening any links and therefore I have no control over this. I have banged my head off this wall before. Another browser causes issues with something else. Bottom line here an expensive product like this should just work.
Nora Jones I completely agree that this is no small issue and it will impact the end user experience and also be detrimental and any piece of learning content.
The fact this has been a re-occurring issue for more than 2 years doesn't fill me with the greatest of confidence that this has been adequately investigated. My only hope is to SCORM my module and upload to my LMS test site. Fingers crossed the SCORMing may negate this issue. Nora Jones I will let you know the outcome of this testing.
We have created SCORM files of our courses and uploaded them to our LMS. The problem still happens. We are using Moodle as our LMS. I have had to put a note prior to the "try me" interactives warning our learners of this issue. Not ideal.
Yes, I'm having the same issue with the scroll bar moving up too high each time content is selected. Really hoping someone posts a fix or upates Rise as it's not a small issue, especially for an expensive product. It really affects the user experience and makes courses look glitchy. It would be the main reason I didn't subscribe.
Hey everyone. I just uploaded my SCORM package to a test LMS environment and am experiencing the same auto-scroll. It's pretty significant and really annoying since we're trying to simulate a software interface and there are so many interactions.
Any update, or work-arounds? Would turning the block entrance animations to off help?Update: turning the block entrance animations off did not help.
Any solutions to the auto-scrolling issue? I have the same issue with Storyline blocks in Rise. It would be nice if we get a solution as this is distracting to the learner.
Hi Martin! We're still working on this possible bug and we'll share any updates here as soon as we have new information. In the meantime here are some recommended workarounds that you can try:
- Make sure the Storyline block is centered on the browser when viewing it.
- If viewed on a laptop or monitor where the screen is small and the Storyline block will appear bigger, you may zoom out of the browser so the entire block is seen on the page.I hope this helps!
Please let me know if there is an update. I'm having the same issue and it's distracting for the learner. It doesn't seem to depend on the browser.
We are facing the same issue, please let me know if there is any update on it.
Hi Krishna,
Sorry to hear you're running into this! I'm curious whether you're experiencing the same issue reported in this thread. That bug causes a Storyline block within Rise to get jumpy when navigating through it, as the block can become off-center. The issue has been resolved in Update 62 of Storyline360.
I see that you are using a newer Storyline version, so this bug should no longer happen. If you still see this behavior, would you be willing to share your Storyline file with us so we can look at what you have set up? You may also share it privately by sending it along in a support case. We'll delete it when we're done testing.
