⚡ Bolt: Optimize scroll-to-top button listener#134
Conversation
Co-authored-by: kaitoartz <56949089+kaitoartz@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: Cached visibility state and added
{ passive: true }to the scroll listener for the scroll-to-top button.🎯 Why: Avoids continuous DOM
classListmanipulation on every scroll event and allows the browser to optimize scrolling without waiting forpreventDefault().📊 Impact: Reduces layout thrashing and main thread blocking during scrolling, freeing up CPU cycles.
🔬 Measurement: Verify scroll-to-top button toggles correctly at 300px threshold with lower CPU usage profiling during rapid scrolls.
PR created automatically by Jules for task 3965983148770198588 started by @kaitoartz