Repository navigation
Many of our components draw outside their paintBounds #71
Description
Thursday Jul 16, 2015 at 22:25 GMT
Originally opened as https://github.com/flutter/engine/issues/26
From @Hixie on July 14, 2015 17:22
You can now easily tell what components paint outside their bounds by turning on debugPaintBoundsEnabled in sdk/lib/base/debug.dart. I noticed at least the following in the stocks app:
- radio buttons
- switches
- anything with shadows, including drawer, popup menu, toolbar, floating action button, dialog
- circles in the stock row
/cc @collinjackson @iansf
Copied from original issue: domokit/mojo#321
Activity
FlutterIssues commentedon Nov 9, 2015
Wednesday Oct 28, 2015 at 02:23 GMT
@abarth Any update on whether we are going to drop the paintBounds concept?
FlutterIssues commentedon Nov 9, 2015
Wednesday Oct 28, 2015 at 02:59 GMT
We can remove paintBounds. There's some chance we'll need it later, but if that happens we can add it back. We should still make most things paint in bounds so they'll hit test and clip correctly.
eseidelGoogle commentedon Nov 16, 2015
Sounds like we can close this?
abarth commentedon Nov 16, 2015
Sure, but we should file a code health bug to remove
paintBoundsfrom the system.Hixie commentedon Nov 16, 2015
And we should probably still verify that the widgets (switch in particular) stay within their bounds. Right now a number of them overflow.
Set ios_deployment_version to iOS 8 (flutter#71)
github-actions commentedon Sep 7, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.