⚡ Bolt: Optimize chat history rendering performance#11
⚡ Bolt: Optimize chat history rendering performance#11
Conversation
- Added Trusted Mode (alwaysAllowReadWrite) to bypass tool confirmations.\n- Added fetch_url alias for web_fetch for agent compatibility.\n- Added UpdateFrontmatterTool and AppendContentTool for improved Bases integration.\n- Updated README.md.\n\nNote: This code was written with Gemini 3 thinking in Google Antigravity.
Co-authored-by: ArnBdev <207385326+ArnBdev@users.noreply.github.com>
…314617928267464 Fix PR feedback: Trusted Mode modal, safety checks, and formatting
- Use `Promise.all` to render chat history messages in parallel instead of sequentially. - Batch scroll operations by disabling individual message scrolling during history load. - Add `shouldScroll` parameter to `displayMessage` to control auto-scrolling. - Implement `scrollToBottom` in `SessionUICallbacks`. This reduces the time to render long chat histories by overlapping asynchronous markdown rendering tasks and avoiding redundant DOM layout thrashing from repeated scroll events. Co-authored-by: ArnBdev <207385326+ArnBdev@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. |
1 participant
💡 What: Optimized chat history loading by parallelizing message rendering and batching scroll operations.
🎯 Why: Loading long chat histories was slow due to sequential processing of markdown rendering and repeated scroll-to-bottom calls for each message.
📊 Impact: Faster loading of chat sessions, especially those with many messages. The rendering of markdown is now concurrent, and DOM layout calculations for scrolling are minimized to once per load.
🔬 Measurement: Verify by loading a session with a long history. Messages should appear more quickly, and the scroll position should jump to the bottom once at the end.
PR created automatically by Jules for task 15388604021704614533 started by @ArnBdev