OpenSlides / OpenSlides/openslides-client

Long motion: Fix jumping to end of a list and double scrollbars

Open
#4,834 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
35
Forks
52
Avg merge
1d 9h
Merged PRs (30d)
52

Description

Describe the bug
When navigating from a motion with long metadata (i.e. several polls) to a different menu, the browser remembers the scrolling position from the previous page.

How to Reproduce

  1. enter a meeting that has >10 participants
  2. create a motion and add at least 3 ended polls (analog is fine)
  3. scroll to the end of the motion page
  4. click on the another menu (you need several items in the list because the possibility for scrolling needs to be possible)
  5. you jump to the end of the list of participants and you see two scrollbars (only in Chromium)

Expected behavior
When navigating to a menu from a long motion, then you should jump to the most upper place of the list and not where the scrollbar was saved

Additional info
This bug and its fix does not relate in any way to other saved scrolling behaviour, e.g. when you scroll down in the agenda, open an item and navigate back.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the navigation flow in Chromium with a long motion, several ended polls, and a long participant list. Trace how scrolling is retained when switching menus and identify the source of the second scrollbar. Done means navigation opens the destination list at the top with one scrollbar, without changing the separate agenda scroll-back behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.