Can we access your project?
Current Behavior
Expandable doesn't control the length of it's expanded section (nor as fix, expandable or expanded). Thus overflow, thus unusable.
Expected Behavior
Expanded section should not overflown the widgets that follow. Expandable should control the length available for expanded section. With dynamic content always full page should be used, but divided among active/shown at the time.
☝️For all widgets : for children that are expandable/expanded flex parameter (i.e., screen space divizion) should be bound to var not just a fix value - so App would be in dynamic control which section is most prominent on the screen. That part is not a bug, it is just a major shortcoming from the UI/UX standpoint. It is almost a "must have" 🫣🤞
Steps to Reproduce
- On a blank page, create a widget tree - column with four or of your choice expandable widgets.
- Put a list (15÷30 items) under each expandable and test.
Reproducible from Blank
Bug Report Code (Required)
IT48ls/l6otPxdtH17qBYMdB/TgWOUs7apEw0OwaSUg8J5TYO5YEZ8/7VEpVZ/2+dkFIPWeakj0y3MKPm9z1KvA5FyebfbVxwaV2ewzjVT+6MqqPBs+CYH9UGshhfRGl58CFrB5NA/Vvc3wg1Fz6ON6tTjDcNpC3PW4jJ+aaOp7XmAfuQ0SLb3kNh1JWeC/v
Visual documentation
Uploaded is code of one widget, but can be tested on all four.
On top are added 4 buttons - to play and turn expandable on/off. <= having dynamic (var bound) flex would help control FULL page to be used. That part not a bug.
Each Expandable causes same overflow.
Environment
- FlutterFlow version: v7.0.14
- Platform: Web
- Browser name and version: Chrome, Version 149.0.7827.197 (Official Build) (64-bit)
- Operating system and version affected: Win 11
Additional Information
Unless widget being misused, great shortcoming; it could be a very powerful UI/UX widget.
Can we access your project?
Current Behavior
Expandable doesn't control the length of it's expanded section (nor as fix, expandable or expanded). Thus overflow, thus unusable.
Expected Behavior
Expanded section should not overflown the widgets that follow. Expandable should control the length available for expanded section. With dynamic content always full page should be used, but divided among active/shown at the time.
☝️For all widgets : for children that are expandable/expanded flex parameter (i.e., screen space divizion) should be bound to var not just a fix value - so App would be in dynamic control which section is most prominent on the screen. That part is not a bug, it is just a major shortcoming from the UI/UX standpoint. It is almost a "must have" 🫣🤞
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT48ls/l6otPxdtH17qBYMdB/TgWOUs7apEw0OwaSUg8J5TYO5YEZ8/7VEpVZ/2+dkFIPWeakj0y3MKPm9z1KvA5FyebfbVxwaV2ewzjVT+6MqqPBs+CYH9UGshhfRGl58CFrB5NA/Vvc3wg1Fz6ON6tTjDcNpC3PW4jJ+aaOp7XmAfuQ0SLb3kNh1JWeC/v
Visual documentation
Uploaded is code of one widget, but can be tested on all four.
On top are added 4 buttons - to play and turn expandable on/off. <= having dynamic (var bound) flex would help control FULL page to be used. That part not a bug.
Each Expandable causes same overflow.
Environment
Additional Information
Unless widget being misused, great shortcoming; it could be a very powerful UI/UX widget.