anomalyco
error Window.getComputedStyle
Description
Technical Analysis
The stack trace points to a minified React/Floating UI update loop (autoUpdate or similar) or a layout measurement hook. The error Window.getComputedStyle requiring an Element instance suggests that a ref.current is null or undefined at the moment of measurement.
This likely happens when:
The Markdown parser enters an incomplete state (e.g., inline code start). The React render cycle triggers. A layout effect tries to measure the dimensions of the code block or surrounding text. The DOM node for that segment is not yet available or is invalid due to the incomplete parsing. Suggested Fixes
Guard getComputedStyle: Ensure the element is an instanceof Element before calling getComputedStyle. Robust Markdown Rendering: Handle incremental Markdown parsing gracefully (e.g., treat unclosed backticks as plain text until closed) to prevent render-phase errors. Error Boundary: Wrap the message list or Markdown renderer in an Error Boundary to catch component-level errors without crashing the entire application window.
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
macOS 26.2
Terminal
No response
