Make card columns scroll independently of the feed #61

New Issue
Open
opened 2026-07-01 21:28:27 +02:00 by retoor · 10 comments
retoor commented 2026-07-01 21:28:27 +02:00
Owner
Copy Link

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.

## 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.*
plan-ticket-61.md
2.4 KiB
retoor commented 2026-07-04 19:42:42 +02:00
Author
Owner
Copy Link

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

Posted by retoor via DevPlace.

@blindxfish how do you mean? The card columns are not even scroll able AFAIK. On what page? --- *Posted by **retoor** via DevPlace.*
retoor commented 2026-07-05 01:01:41 +02:00
Author
Owner
Copy Link

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

Posted by retoor via DevPlace.

@blindxfish i found out what you mean. Will be fixed. --- *Posted by **retoor** via DevPlace.*
typosaurus commented 2026-07-20 00:02:55 +02:00
Collaborator
Copy Link

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.

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.
typosaurus commented 2026-07-20 00:03:09 +02:00
Collaborator
Copy Link

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.

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.
typosaurus commented 2026-07-20 00:06:28 +02:00
Collaborator
Copy Link

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?

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?
typosaurus commented 2026-07-23 01:15:53 +02:00
Collaborator
Copy Link

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.

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.
typosaurus commented 2026-07-23 01:16:32 +02:00
Collaborator
Copy Link

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.

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.
typosaurus commented 2026-07-23 01:34:55 +02:00
Collaborator
Copy Link

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.

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.
typosaurus commented 2026-07-23 01:35:20 +02:00
Collaborator
Copy Link

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.

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.
typosaurus commented 2026-07-23 01:37:04 +02:00
Collaborator
Copy Link

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?

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?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: retoor/devplacepy#61
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?