mirror of
https://github.com/kuhyx/todo-app.git
synced 2026-11-13 19:11:01 +01:00
Krzysztof kuhy Rudnicki
032376a4d7
Found via on-device testing after the earlier warm-palette commit: the View/Guided/Raw SegmentedButton's selected segment rendered in Flutter's stock Material teal, not the warm palette. Neither ColorScheme.light() nor .dark() defined secondary/tertiary (or their container/on- variants), so any M3 widget reaching for secondaryContainer (SegmentedButton, Chips, etc.) silently fell back to the framework default instead of erroring -- a gap invisible in static review or widget tests, only visible rendered. The shared palette has one accent, not a separate secondary hue, so these mirror primary; secondaryContainer/tertiaryContainer use the line-light/ line-dark border color as a distinguishable-but-subtle selected-state fill. Verified: flutter analyze clean, 188/188 tests at 100% coverage, re- verified identical in an isolated worktree, and confirmed live on the physical phone (adb install -r + screenshot) -- the Raw tab now renders gold/amber instead of teal. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| data | ||
| desktop | ||
| sync | ||
| ui | ||
| frame_stats_io.dart | ||
| frame_stats_web.dart | ||
| frame_stats.dart | ||
| main.dart | ||