Summary
The Reflection Widget schedules its initial "Reading code" typing indicator with a delayed setTimeout(), but that timeout is not cancelled if the export/API request finishes before the delay expires.
Steps to reproduce
- Open the Reflection Widget in Music Blocks.
- Use a fast backend response or a small/simple project so startup completes in under 1 second.
- Wait briefly after the first assistant response appears.
Actual behavior
A delayed typing indicator can appear after the response is already rendered, and it may remain visible until another request clears it.
Expected behavior
If startup finishes before the delayed indicator appears, the pending timeout should be cancelled so no stale typing indicator is shown.
Likely root cause
startChatSession() schedules showTypingIndicator("Reading code") with setTimeout(...), but hideTypingIndicator() only removes an already-rendered indicator and does not clear the pending timeout.
Affected file
Summary
The Reflection Widget schedules its initial "Reading code" typing indicator with a delayed
setTimeout(), but that timeout is not cancelled if the export/API request finishes before the delay expires.Steps to reproduce
Actual behavior
A delayed typing indicator can appear after the response is already rendered, and it may remain visible until another request clears it.
Expected behavior
If startup finishes before the delayed indicator appears, the pending timeout should be cancelled so no stale typing indicator is shown.
Likely root cause
startChatSession()schedulesshowTypingIndicator("Reading code")withsetTimeout(...), buthideTypingIndicator()only removes an already-rendered indicator and does not clear the pending timeout.Affected file
js/widgets/reflection.js