buildBlenderHeader (lib/editor_shared/chrome/blender_header.dart) is a single Row of chrome that does not wrap, collapse or scroll, and no minimum window size is set anywhere - WindowOptions in main.dart sets only titleBarStyle, skipTaskbar and windowButtonVisibility.
Measured by bisecting the boot smoke test surface: it fits at 1800 logical px and overflows by 22px at 1700, so the threshold sits around 1750 in a DEBUG build. Release is slightly cheaper because the kDebugMode "Buy a License" stub drops out, but not by much.
That is wider than a 1440pt or 1512pt laptop screen. Anyone running the editor windowed rather than maximised on a laptop gets a yellow-and-black overflow stripe across the header.
The overflow reports against the inner Row at blender_header.dart:101 - the perf metrics group inside the drag area - because that is the flexible child that gets squeezed, but the cause is the total intrinsic width of the bar rather than that group specifically.
Note this was being masked: test/widget_test.dart pumped at the default 800x600 and had been failing on the resulting overflow for long enough that the failure read as "stale smoke test". It now pumps at 1900x1000 with the measurement recorded in a comment, so it fails for boot reasons only and this issue owns the layout.
Opened during the roadmap audit on 2026-09-05.
`buildBlenderHeader` (`lib/editor_shared/chrome/blender_header.dart`) is a single Row of chrome that does not wrap, collapse or scroll, and no minimum window size is set anywhere - `WindowOptions` in `main.dart` sets only `titleBarStyle`, `skipTaskbar` and `windowButtonVisibility`.
Measured by bisecting the boot smoke test surface: it fits at 1800 logical px and overflows by 22px at 1700, so the threshold sits around 1750 in a DEBUG build. Release is slightly cheaper because the `kDebugMode` "Buy a License" stub drops out, but not by much.
That is wider than a 1440pt or 1512pt laptop screen. Anyone running the editor windowed rather than maximised on a laptop gets a yellow-and-black overflow stripe across the header.
The overflow reports against the inner Row at `blender_header.dart:101` - the perf metrics group inside the drag area - because that is the flexible child that gets squeezed, but the cause is the total intrinsic width of the bar rather than that group specifically.
Note this was being masked: `test/widget_test.dart` pumped at the default 800x600 and had been failing on the resulting overflow for long enough that the failure read as "stale smoke test". It now pumps at 1900x1000 with the measurement recorded in a comment, so it fails for boot reasons only and this issue owns the layout.
Opened during the roadmap audit on 2026-09-05.
ImBenji
added this to the Arcs & Angles project 2026-09-05 15:11:30 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
buildBlenderHeader(lib/editor_shared/chrome/blender_header.dart) is a single Row of chrome that does not wrap, collapse or scroll, and no minimum window size is set anywhere -WindowOptionsinmain.dartsets onlytitleBarStyle,skipTaskbarandwindowButtonVisibility.Measured by bisecting the boot smoke test surface: it fits at 1800 logical px and overflows by 22px at 1700, so the threshold sits around 1750 in a DEBUG build. Release is slightly cheaper because the
kDebugMode"Buy a License" stub drops out, but not by much.That is wider than a 1440pt or 1512pt laptop screen. Anyone running the editor windowed rather than maximised on a laptop gets a yellow-and-black overflow stripe across the header.
The overflow reports against the inner Row at
blender_header.dart:101- the perf metrics group inside the drag area - because that is the flexible child that gets squeezed, but the cause is the total intrinsic width of the bar rather than that group specifically.Note this was being masked:
test/widget_test.dartpumped at the default 800x600 and had been failing on the resulting overflow for long enough that the failure read as "stale smoke test". It now pumps at 1900x1000 with the measurement recorded in a comment, so it fails for boot reasons only and this issue owns the layout.Opened during the roadmap audit on 2026-09-05.