Skip to content

⚡ Bolt: Optimize scroll performance and TOC rendering#1

Open
VagueDustin wants to merge 1 commit into
mainfrom
bolt-performance-scroll-toc-14106035736568216985
Open

⚡ Bolt: Optimize scroll performance and TOC rendering#1
VagueDustin wants to merge 1 commit into
mainfrom
bolt-performance-scroll-toc-14106035736568216985

Conversation

@VagueDustin

Copy link
Copy Markdown
Owner

💡 What:

Optimized the scroll handling and Table of Contents (TOC) rendering logic in the main App component.

🎯 Why:

The previous implementation updated React state on every scroll tick and performed expensive DOM queries (querySelectorAll) and layout calculations (getBoundingClientRect) on each event. This led to frequent full-app re-renders and potential frame drops, especially in large documents.

📊 Impact:

  • Zero re-renders of the App component during scrolling (unless the active heading changes).
  • Reduced DOM overhead by caching headings instead of querying them 60+ times per second.
  • Smoother loading experience by yielding the main thread to allow the "Loading..." state to render before heavy parsing starts.

🔬 Measurement:

  • Verified with npm run lint and npm run build.
  • Visual verification via Playwright showed smooth progress bar updates and correct TOC highlighting without lag.

PR created automatically by Jules for task 14106035736568216985 started by @VagueDustin

- Implemented direct DOM updates for the progress bar using a Ref to bypass React's re-render cycle during scrolls.
- Throttled the scroll listener using requestAnimationFrame for better performance.
- Cached headings in a Ref to eliminate repeated querySelectorAll calls during scrolls.
- Extracted and memoized TOCItem component, with useCallback for its click handler, to minimize TOC re-renders.
- Wrapped heavy synchronous markdown processing in setTimeout to improve perceived performance by allowing the loading spinner to paint.
- Fixed existing lint errors and restored window title persistence on file changes.

Co-authored-by: VagueDustin <127912586+VagueDustin@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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