Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Library page - When scrolling to the bottom the page glitches #13170

Open
DuarteRamires opened this issue Mar 7, 2025 · 2 comments
Open

Library page - When scrolling to the bottom the page glitches #13170

DuarteRamires opened this issue Mar 7, 2025 · 2 comments

Comments

@DuarteRamires
Copy link

Observed behavior

When scrolling through libraries with a small number of folders, the page glitches continuously once you reach the bottom. This issue stops when scrolling back up. The problem does not occur on pages with a large number of folders, where scrolling is required to reach the bottom.

Video:

https://drive.google.com/file/d/1qxNibTRRREAzZLNeRZcGfCniVfMfbPD9/view?usp=sharing

Expected behavior

When reaching the bottom of a library page, the page should not exhibit any visual glitches, and scrolling should function smoothly without issues.

User-facing consequences

Users experience a distracting visual glitch when navigating libraries with fewer folders, affecting the overall user experience.

Steps to reproduce

  1. Install the latest develop build.
  2. Navigate to Learn > Library and open a library page with a small number of folders.
  3. Scroll to the bottom of the page to observe the glitch.

Context

  • Kolibri version: 18
  • Operating system: Windows 11, Ubuntu
  • Browser: All browsers
@DuarteRamires
Copy link
Author

I would like to contribute by fixing this bug as my first issue

@marcellamaki
Copy link
Member

Hi @DuarteRamires - thank you for opening this issue and for your interest in contributing. There have been several related issues filed over time (and several times that we have thought we "fixed" this problem, which has come back to haunt me) and you'll find some context here: #10663 (which also has a duplicate issue linked).

If you'd like to take this up, you can do so, but please share here your planned approach first as a comment before getting started with coding/opening a PR. Feel free to ask any follow up questions after reading the linked issue thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants