Forum Discussion

DelaneyColly206's avatar
DelaneyColly206
Community Member
5 months ago
Solved

Rise course published to HTML - scrolling issue

Hello,

I've created a Rise course to host on a client website. It is published as an HTML file, and they have uploaded it to the host site. However, in testing it, I have discovered some odd behavior: on each new page or section that I reveal, it automatically scrolls to the bottom (sometimes even beyond the content).

You can see what I mean here: https://www.hcu.edu/academics/distance-learning/prospective-dl-students/online-learning-readiness-survey/ 

Obviously this could confuse users. Has anyone else had this issue? Do you know what's going on? Any tips to fix it?

Thanks!

Delaney

  • The use of the iframe is causing this. On mobile there are other issues- some pages don't seem to scroll and you're stuck at the top.

8 Replies

  • P.S. There are other updates I need to make too, so please ignore some of the other UX stuff - I just need help with the scrolling problem!

  • PhilFoss's avatar
    PhilFoss
    Community Member

    The use of the iframe is causing this. On mobile there are other issues- some pages don't seem to scroll and you're stuck at the top.

    • DelaneyColly206's avatar
      DelaneyColly206
      Community Member

      It's somehow reassuring to hear it's not just me... Have you found any way to work around this?

      • PhilFoss's avatar
        PhilFoss
        Community Member

        I would get rid of the iframe, and create an abbreviated version of your header that persists at the top of the course that would give the user a link 'back to main' site.

         

  • vercel's avatar
    vercel
    Community Member

    It sounds like the auto-scrolling issue might be caused by a JavaScript event triggering on new content loads, possibly focusing on an element at the bottom of the page. Try checking if there are any autofocus attributes, scroll-related JavaScript functions, or unintended interactions with iframes. You can also inspect the console for errors or conflicts that might be causing this behavior. If the issue persists, testing in different browsers or disabling scripts temporarily could help identify the culprit. Let me know if you need help debugging further!