Display Flutter errors (or similar) when the layout is broken
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17k
- Forks
- 694
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 33
Description
Please Describe The Problem To Be Solved
In Flutter, if we make a problematic layout where a child widget tries to take the maximum height/width of a parent widget that does not have a maximum height/width, a viewport was given an unbounded height/width error will be printed in the console.

More information about this problem can be found in this video on the Flutter YouTube channel:
Also, if a widget is trying to get more space than what is available (overflow), we get a visual indicator on how many pixels are not displayed:
Unfortunately, we don't have this important feedback in Flet. All we get is a layout that has something unexpected (no scrolling or incomplete control). Beginners often struggle a lot to learn Flet because of these problems (especially the first). In fact, if you check the Discord server, almost every new one is facing these problems and does not know how to solve them or even how to properly describe them because no error is shown. It would be very useful to have feedback similar to what we get in Flutter.
(Optional): Suggest A Solution
Show similar errors to what Flutter shows for its users.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Flet's layout and rendering handling, then compare its behavior with the Flutter unbounded-constraints and overflow examples described in the issue. Done means broken layouts provide actionable feedback similar to Flutter rather than only appearing incomplete or non-scrolling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flutter, python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100
