QA Session Recordings

# linux QA Video Report - Generated at: 2026-04-12T13:25:53.238Z - Model: `gemini-3-flash-preview` - Target: https://github.com/Comfy-Org/ComfyUI_frontend/issues/7942 - Source video: `./qa-artifacts/qa-report-Linux-24307554488/qa-session.mp4` - Video size: 675.1 KB ## AI Review ## Summary The video successfully reproduces Issue #7942: "Gap between DOM and built-in widgets after node resize." The recording demonstrates that when a built-in widget (a button) is added after a DOM widget (a text area), resizing the node causes the button to anchor to the bottom of the node, creating an unintended vertical gap between the two widgets. ## Confirmed Issues ### Gap between DOM and built-in widgets after node resize `MEDIUM` `00:12` `Confidence: High` When the node is resized vertically, a large empty gap appears between the DOM text area widget and the built-in button widget located below it. The built-in widget remains anchored to the bottom of the node frame instead of maintaining its relative position directly beneath the preceding DOM widget. This confirms the reported layout bug in the Nodes 2.0 UI system where DOM widgets and built-in widgets do not correctly share available space during a resize if the DOM widget is first. **Evidence:** At 00:12, as the cursor drags the node's resize handle downward, the distance between the "text, watermark" input field and the "qa_test_button" increases significantly, leaving a large grey empty area. **Suggested Fix:** Adjust the CSS grid or layout logic for Nodes 2.0 to ensure that built-in widgets following DOM widgets are not forced to anchor to the bottom of the node. The layout should likely treat the sequence of widgets as a continuous flow where the DOM widget takes up flexible space or the built-in widget is positioned relative to the element above it rather than the node container's bottom. --- ## Possible Issues (Needs Human Verification) No other issues were observed. ## Overall Risk `low` This is a purely visual/UI layout issue that does not appear to break the functionality of the nodes or the workflow, as noted in the original issue description. ## Narration The video contains a TTS narration track: "Here is a CLIPTextEncode node. Its text input is a DOM widget. We have also added a built-in button widget after the DOM widget — matching the bug conditions from the issue. Now we resize the node by dragging its bottom-right corner downward. The bug is evident: a large empty gap now appears between the DOM textarea widget and the built-in button widget. The button has anchored to the bottom of the node instead of staying directly below the DOM widget." ## Verdict {"verdict": "REPRODUCED", "risk": "low", "confidence": "high", "narrationDetected": true}