#61

Make card columns scroll independently of the feed

Status: open
blindxfish blindxfish ·

Summary

Scrolling the card column should not require scrolling through the entire feed; columns should scroll independently based on mouse position.

Steps to Reproduce

  1. Open a page with a feed and card columns (sidebars).
  2. Attempt to scroll a card column using the mouse.
  3. Observe that the entire feed scrolls instead of the targeted column.

Expected Behaviour

Each card column should scroll independently when the mouse is over it, without affecting the main feed.

Actual Behaviour

Scrolling a card column causes the entire feed to scroll, requiring the user to navigate through the full feed to reach content in the sidebars.

Environment

Not provided.


Reported by blindxfish via DevPlace.

Updates & comments

retoor retoor ·

@blindxfish how do you mean? The card columns are not even scroll able AFAIK. On what page?


Posted by retoor via DevPlace.

retoor retoor ·

@blindxfish i found out what you mean. Will be fixed.


Posted by retoor via DevPlace.

Developer reply from dev typosaurus ·

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

Developer reply from dev typosaurus ·

Starting research round 1 of at most 5.

I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.

Developer reply from dev typosaurus ·

The ticket was compared against the current source and tests at HEAD. The fix described in the body has already been applied across all affected pages, and the claimed bug no longer replicates in the present codebase.

This does not appear to match the current state of the code. Could you confirm whether this is still accurate, or should the ticket be closed?

Developer reply from dev typosaurus ·

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

Developer reply from dev typosaurus ·

I need input to continue.

What I tried: Retried this step 3 times.
What I found: Each attempt failed for internal reasons unrelated to this ticket. The details are in the operator's logs; this is not a judgment about the ticket.

The system needs operator attention before I can continue. Reply here once things are healthy and I will resume from where I left off.

Developer reply from dev typosaurus ·

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

Developer reply from dev typosaurus ·

Starting research round 1 of at most 5.

I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.

Developer reply from dev typosaurus ·

After reviewing the current source code and tests across all affected pages (feed, projects, gists), I have confirmed that the exact behavior requested - independent scrolling for card columns via position: sticky, max-height, and overflow-y: auto on both sidebars - is already implemented and in production. The described bug does not reproduce, and no clarifying comments from the reporter have been provided.

This ticket appears to describe a fix that is already live. Could you confirm whether this issue remains accurate, or should the ticket be closed?

Log in to comment.