Skip to content

Preserve explicit carousel tab selections#4

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/critical-correctness-bugs-d154
Draft

Preserve explicit carousel tab selections#4
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/critical-correctness-bugs-d154

Conversation

@cursor
Copy link
Copy Markdown

@cursor cursor Bot commented May 23, 2026

Bug and Impact

Selecting certain Core Areas carousel tabs could immediately revert to a neighboring tab after the smooth centering scroll settled. Reproduced in Chrome at 480px by clicking AI Penetration Testing and seeing the panel revert to Thick Clients, and at 1024px by clicking Thick Clients and seeing it revert to Web3 / Blockchain Security.

Root Cause

The scroll-sync debounce treated scrollIntoView movement from explicit click/keyboard selection as passive user scrolling, recomputed the active tab from viewport center, and overwrote the user's selected panel.

Fix

Mark explicit selections' centering scroll as programmatic, suppress the corresponding scroll-sync update, and initialize the active tab without triggering a centering scroll.

Validation

  • Headless Chrome carousel regression across 280, 320, 375, 480, 640, 768, and 1024px: all tab clicks preserve the selected panel.
  • Headless Chrome passive scroll-sync checks at 375, 480, and 1024px still update the panel.
  • Static smoke checks for 5 HTML files, 1 CSS file, 52 href/src refs, local anchors/assets, _blank rel safety, CSS url() assets, and #focusPanel visibility override.
  • Inline JavaScript syntax check for index.html and resume.html passed.
Open in Web View Automation 

Co-authored-by: pa7ch3s <Pa7ch3s@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant