From 25d3f35b5580bbe13a9e39fb1d87609a350f0d48 Mon Sep 17 00:00:00 2001 From: ChuckBuilds Date: Mon, 7 Sep 2026 09:56:37 -0400 Subject: [PATCH] chore: leave visual_display_manager untouched so #523 can merge The only change this branch made to that file was a docstring, and it collided with #523's rewrite of the same method -- so #534 and #523 each merged cleanly against main but conflicted with each other. Reverted to main's text; #523 owns this method and adds frame_hold to it. The note the docstring carried ('frame_hold arrives in #523') would have been stale the moment #523 landed anyway. The parity test in #523 is what actually keeps the two signatures honest. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_014RRtqXDCnvnY6EQwhT5CV9 --- src/plugin_system/testing/visual_display_manager.py | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/src/plugin_system/testing/visual_display_manager.py b/src/plugin_system/testing/visual_display_manager.py index 82cab907..e33d2309 100644 --- a/src/plugin_system/testing/visual_display_manager.py +++ b/src/plugin_system/testing/visual_display_manager.py @@ -507,15 +507,7 @@ class VisualTestDisplayManager: # ------------------------------------------------------------------ def set_scrolling_state(self, is_scrolling: bool): - """Set the current scrolling state (no-op for testing). - - Deliberately mirrors DisplayManager.set_scrolling_state exactly. A - double that accepts arguments production does not lets a call pass - every harness run and then raise TypeError on the panel, which is the - one failure a safety harness exists to prevent. ``frame_hold`` arrives - here in the same change that adds it to DisplayManager (#523), not - before. - """ + """Set the current scrolling state (no-op for testing).""" self._scrolling_state['is_scrolling'] = is_scrolling if is_scrolling: self._scrolling_state['last_scroll_activity'] = time.time()