Blog page remains scrolled down after navigating to next page #53

Open
opened 2025-09-22 00:55:46 -04:00 by rokit · 2 comments

Issue URL:

https://www.topcoder.com/blog

Steps to reproduce

  1. Go to https://www.topcoder.com
  2. Under Resources, Click "Blog"
  3. Scroll to the section with pages sections(1,2,3,4...)
  4. Click next as page 2, the content is only displayed from the bottom of the content due to improper defined scroll behaviour of javascript code.
  5. The content should direct user from top of blogs after clicking next page
  6. Observe

Actual result

improperly defined scroll behavior,scrolling or content-rendering logic after clicking page 2 or others doesnt scroll from top automatically after the user clicks.

Expected result

The JavaScript function responsible for handling the "Next" button's click event might be trying to scroll to a specific element, but the element doesn't exist or is not set up correctly. The content should be displayed from the top

Screenshots/Videos

Environment

OS and Browser version:Windows 10 pro Google chrome Version 140.0.7339.128 (Official Build) (64-bit)

Device: DESKTOP-A2KPPT3 Processor Intel(R) Core(TM) i5-9600 CPU

Reproducibility

Happens everytime

#### Issue URL: https://www.topcoder.com/blog #### Steps to reproduce 1. Go to https://www.topcoder.com 2. Under Resources, Click "Blog" 3. Scroll to the section with pages sections(1,2,3,4...) 4. Click next as page 2, the content is only displayed from the bottom of the content due to improper defined scroll behaviour of javascript code. 5. The content should direct user from top of blogs after clicking next page 6. Observe #### Actual result improperly defined scroll behavior,scrolling or content-rendering logic after clicking page 2 or others doesnt scroll from top automatically after the user clicks. #### Expected result The JavaScript function responsible for handling the "Next" button's click event might be trying to scroll to a specific element, but the element doesn't exist or is not set up correctly. The content should be displayed from the top #### Screenshots/Videos <video src="attachments/88960051-7aa8-4043-89c7-3ea778886bee" title="Screencast 2025-09-22 07-55-14.webm" controls></video> #### Environment OS and Browser version:Windows 10 pro Google chrome Version 140.0.7339.128 (Official Build) (64-bit) Device: DESKTOP-A2KPPT3 Processor Intel(R) Core(TM) i5-9600 CPU #### Reproducibility Happens everytime
rokit added the WindowsChromeFunctional labels 2025-09-22 00:55:46 -04:00
nithya160925 added UXvalid and removed Functional labels 2025-09-24 04:50:43 -04:00
nithya160925 added the S: Low label 2025-09-24 04:52:11 -04:00
nithya160925 added the P: Blog label 2025-09-25 05:06:36 -04:00
nithya160925 changed title from improperly defined scroll behavior,scrolling or content-rendering logic after clicking page 2 or others doesnt scroll from top automatically to Blog page remains scrolled down after navigating to next page 2025-09-26 06:02:42 -04:00
Collaborator

Let's use the behavior of the repository's issue list pagination (the one we are on right now) as a reference. When a user clicks to a new page, the view should automatically scroll to the top of the content.

Let's use the behavior of the repository's issue list pagination (the one we are on right now) as a reference. When a user clicks to a new page, the view should automatically scroll to the top of the content.
Collaborator

Also, while working on the pagination component for this scroll fix, please review the suggestion in Issue #167 regarding adding First and Last page navigation links. It may be efficient to implement that enhancement at the same time.

Also, while working on the pagination component for this scroll fix, please review the suggestion in Issue #167 regarding adding First and Last page navigation links. It may be efficient to implement that enhancement at the same time.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Topcoder-Platform/public-website-qa-bug-hunt#53