{"version":"2.1.267","anchor":"ui-element-tree-validator-used-to-check-what-gets-rendered","canonical_anchor":"ui-element-tree-validator-used-to-check-what-gets-rendered","heading":"UI element-tree validator (used to check what gets rendered around dialogs) gained hover-scope and Box-key checks","tier":"internal","area":"Plugin UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/ui-element-tree-validator-used-to-check-what-gets-rendered","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### UI element-tree validator (used to check what gets rendered around dialogs) gained hover-scope and Box-key checks\n\nInternal UI validator adds hover and layout checks and clearer error messages for dialog rendering\n\n**What**\n\nClaude Code's internal check that validates what can be drawn on screen (used when rendering dialogs and overlays) now tracks additional context called 'hoverScope' and 'siblingBoxKeys', and rejects a `Box` component's `hover.display` setting when it's placed around a dialog. It also gives a clearer error message when a `Button`'s properties are misused, and a friendlier error for an unrecognized UI element that now lists the valid element names.\n\n**Why**\n\nThese are internal correctness checks for how Claude Code's own interface is built, but the improved error messages mean any related bug shows up as a much more useful message rather than a cryptic one.\n\n- Area: Plugin UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}