flutter-responsive-layout ยท diff
git:20260827.be30b45 to git:20260905.2eea1ce
4 added, 2 removed. Audit A to A.
---
name: flutter-responsive-layout
- description: Build or repair adaptive Flutter layouts across devices, constraints, breakpoints, overflow, orientation, and input modes. Use with flutter-accessibility when text scaling causes reflow, clipping, or disappearing controls; not for general widget state architecture.
+ description: Build or repair adaptive Flutter layouts across devices, constraints, breakpoints, overlap, clipping, orientation, and input modes. Use with flutter-accessibility when text scaling causes reflow, clipping, or disappearing controls; not for general widget state architecture.
---
# Flutter Responsive Layout
Design from the constraints supplied by the parent, not from a guessed device model.
## Diagnose
- Reproduce the layout on the failing viewport with text scaling and the relevant platform chrome. Read the first meaningful constraint or overflow failure and identify which widget imposed the incompatible size.
+ Reproduce the layout on the failing viewport with text scaling and the relevant platform chrome. Read the first meaningful constraint or overflow failure and identify which widget imposed the incompatible size. When no framework exception occurs, inspect the geometry and hit-test behavior of the affected components instead of assuming that a clean console proves the layout is usable.
## Rules
- Use `LayoutBuilder` when a subtree responds to local constraints and `MediaQuery` when behavior depends on window or accessibility properties.
- Choose a small set of content-driven breakpoints; do not branch on specific device names.
- Prefer flexible constraints, wrapping, scrolling, or alternate composition over fixed width/height patches.
- Keep readable content widths on large displays instead of stretching every element.
- Adapt navigation and information density when space changes materially.
- Respect safe areas, display features, keyboard insets, text scaling, and both pointer and touch input.
- Avoid `IntrinsicHeight` or repeated intrinsic measurement on hot, complex trees without evidence.
## Verification
Exercise boundary widths just below and above each breakpoint, long localized strings, large text, landscape, and the intended desktop/web window sizes. Add a focused widget or golden test for regressions that visual assertions can represent reliably.
+
+ When components overlap, become clipped, or cover an action, follow the [geometry, viewport, and fixture testing reference](references/geometry-viewport-and-fixture-testing.md). Define explicit spatial relationships for important components rather than treating every intersecting render box as a defect.
## References
When adaptive navigation is in scope, follow the [adaptive navigation patterns reference](references/adaptive-navigation-patterns.md).
## Sources
- [Adaptive and responsive design](https://docs.flutter.dev/ui/adaptive-responsive)
- [Building responsive layouts](https://docs.flutter.dev/ui/adaptive-responsive/best-practices)