Files
ComfyUI_frontend/browser_tests/tests
Connor Byrne d0e617af49 fix: refresh DomWidget disabled/clipping when non-reactive sources change
The per-frame mutation optimization broke two cases where DomWidget style
depends on values outside widgetState:

1. widget.computedDisabled is set by litegraph when an input is connected.
   The previous deep-watch on widgetState picked it up incidentally because
   pos/size were rewritten every frame; with equality-checked writes the
   secondary watcher never re-fires, so the connected widget no longer
   renders at opacity 0.5.

2. DomWidget clipping is computed against the selected node's renderArea
   (non-reactive). When the selected node is dragged, only its own widget's
   pos changes — widgets owned by other nodes never re-run updateDomClipping
   and their clip-path stays stale, so a background widget bleeds through
   the foreground node.

Mirror computedDisabled into widgetState each frame and treat selected-node
movement the same as a viewport change (force pos reassignment to refire
the downstream watcher). Restore the bot-regenerated baselines for the two
affected screenshot tests.
2026-05-04 14:15:04 -07:00
..