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

Bug: Scrolling Timeline Feed Affects Active Tasks Column on /me Route #10648

Closed
iamsmruti opened this issue Jan 8, 2025 · 2 comments · Fixed by #10649
Closed

Bug: Scrolling Timeline Feed Affects Active Tasks Column on /me Route #10648

iamsmruti opened this issue Jan 8, 2025 · 2 comments · Fixed by #10649
Labels
bug p4 Should be addressed eventually

Comments

@iamsmruti
Copy link
Contributor

Issue - Bug

  • How serious is the bug? P4
  • OS: All (e.g. macOS, Linux, Windows)
  • Browser: All (e.g. Chrome, Safari, Lynx)
  • Node version: v20.18.1
  • NPM version: v10.8.2

Description

On the /me route in the Parabol application, there are two columns:

  1. Timeline Feed
  2. Active Tasks
    When the timeline feed grows vertically, scrolling affects the entire page instead of only the timeline feed. The expected behavior is that only the timeline feed column should scroll while the rest of the layout, including the "Active Tasks" column, remains static.
Screenshot 2025-01-08 at 10 58 11 PM

Steps to Reproduce

  1. Navigate to the /me page.
  2. Populate the Timeline Feed column with a large number of entries, causing it to overflow vertically.
  3. Attempt to scroll the Timeline Feed.

Actual Behavior

  • Scrolling moves the entire page.

Expected Behaviour

  • Only the Timeline Feed column should scroll, leaving the "Active Tasks" column static.

Acceptance Criteria

Users can:

  • Scroll through the timeline feed independently of the "Active Tasks" column.
  • The layout remains unaffected by vertical overflow in the timeline feed.

Estimated effort: 1 hour to triage.

@iamsmruti iamsmruti added the bug label Jan 8, 2025
@jordanh jordanh added the p4 Should be addressed eventually label Jan 8, 2025
@jordanh
Copy link
Contributor

jordanh commented Jan 8, 2025

Thank you for your report!

@github-project-automation github-project-automation bot moved this to To triage in Product Jan 8, 2025
@iamsmruti
Copy link
Contributor Author

iamsmruti commented Jan 8, 2025

I have created a fix PR, @jordanh would you mind having a look? And put your opinions there

@github-project-automation github-project-automation bot moved this from To triage to Done in Product Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug p4 Should be addressed eventually
Projects
Status: Done
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants