Some of our controls can't handle being built in 0x0 environments

We should create tests that put each UI control into a 0x0 container and make sure they don't crash.

See also #5259 which triggers this in release and debug --no-hot mode.

Add support for text shadows and roll engine (26 commits) (#22449)

@ahmedsameha1

This issue is assigned to @ahmedsameha1 but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

This issue is assigned to @ahmedsameha1 but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

I am actively working on the issue, as you can see from the linked PRs.

@ahmedsameha1

This issue was assigned to @ahmedsameha1 but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

@victorsanni

This issue was assigned to @ahmedsameha1 but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

I am actively working on this issue.
@victorsanni @dkwingsmt

There sure has been tons of status updates, which can be seen from the related PRs. :)

@loic-sharma

This issue was assigned to @ahmedsameha1 but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

Hi @loic-sharma, would you reassign this issue to me?

Done!

Done!

Thank you.

@dkwingsmt

These are widgets that I think need to be handled in this issue. I will work on them one by one as I can, and if I fail, I will report my attempt here.
Magnifier
SliverReorderableList
SnackBar
TextSelectionToolbar
CupertinoAdaptiveTextSelectionToolbar
CupertinoDatePicker
CupertinoActionSheet
CupertinoTextMagnifier
CupertinoSliverNavigationBar
CupertinoNavigationBarBackButton
CupertinoSlidingSegmentedControl
CupertinoSliverRefreshControl
CupertinoPageTransition
CupertinoFullscreenDialogTransition
CupertinoSheetTransition
CupertinoTheme
RenderObjectToWidgetAdapter
DecoratedSliver
PinnedHeaderSliver
PreferredSize
SliverAnimatedOpacity
SliverAnimatedList
SliverAnimatedGrid
ViewAnchor
ViewCollection
RawView: Failed assertion
SliverReorderableList
SliverSafeArea
RawScrollbar
SliverFillViewport
SliverFillRemaining
SliverVisibility
SliverFadeTransition
SystemContextMenu
SliverToBoxAdapter
SliverPadding
SliverSemantics
ListBody
I think that there are no widgets other than the above list and these widgets that are not handled for this issue.
Please notice that I have a pending work that contains 8 widgets, and I am waiting to complete the suggested 10 widgets.
@dkwingsmt @victorsanni

This is my attempt to handle this issue for SnackBar:

  testWidgets('SnackBar does not crash at zero area', (WidgetTester tester) async {
    tester.view.physicalSize = Size.zero;
    addTearDown(tester.view.reset);
    await tester.pumpWidget(
      MaterialApp(
        home: Center(
          child: Scaffold(body: Builder(
            builder: (context) {
              Timer.run(
                () =>
                    [ScaffoldMessenger.of](http://scaffoldmessenger.of/)(context).showSnackBar(const SnackBar(content: Text('X'))),
              );
              return const Placeholder();
            },
          ),
          ),
        ),
      ),
    );
    await tester.pumpAndSettle();
    expect(tester.getSize(find.byType(SnackBar)), Size.zero);
  });

The test fails with:
The _ScaffoldLayout custom multichild layout delegate tried to lay out the child with id "_ScaffoldSlot.snackBar" more than once. Each child must be laid out exactly once.
I need further guidance.
This is my attempt to handle this issue for SnackBar:

  testWidgets('SnackBar does not crash at zero area', (WidgetTester tester) async {
    tester.view.physicalSize = Size.zero;
    addTearDown(tester.view.reset);
    await tester.pumpWidget(
      MaterialApp(
        home: Center(
          child: Scaffold(body: Builder(
            builder: (context) {
              Timer.run(
                () =>
                    [ScaffoldMessenger.of](http://scaffoldmessenger.of/)(context).showSnackBar(const SnackBar(content: Text('X'))),
              );
              return const Placeholder();
            },
          ),
          ),
        ),
      ),
    );
    await tester.pumpAndSettle();
    expect(tester.getSize(find.byType(SnackBar)), Size.zero);
  });

The test fails with:
The _ScaffoldLayout custom multichild layout delegate tried to lay out the child with id "_ScaffoldSlot.snackBar" more than once. Each child must be laid out exactly once.
I need further guidance.

@ahmedsameha1

This issue is assigned to @ahmedsameha1 but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

@ahmedsameha1

This issue is assigned to @ahmedsameha1 but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

@ahmedsameha1

@ahmedsameha1 any idea where our progress is on getting this fixed for all of our relevant widgets?

@justinmc

@justinmc Please check #6537 (comment)
The 8 widgets that I did not push in a PR are: Viewport, ColoredBox, StatefulBuilder, Builder, RawImage, RichText, Flow, Wrap.
Clearly I have not work on this issue for a while and I think I will need some help if I will complete the remaining widgets.

Got it, thanks! I'll go ahead and unassign you.

Navigation Menu

Repository navigation

Some of our controls can't handle being built in 0x0 environments #6537

310 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Some of our controls can't handle being built in 0x0 environments #6537

Description

Activity

Hixie commented on Oct 26, 2016

310 remaining items

flutter-triage-bot commented on Dec 27, 2025

ahmedsameha1 commented on Dec 28, 2025

flutter-triage-bot commented on Mar 15, 2026

ahmedsameha1 commented on Mar 15, 2026

dkwingsmt commented on Mar 16, 2026

ahmedsameha1 commented on Mar 16, 2026

dkwingsmt commented on Mar 16, 2026

ahmedsameha1 commented on Mar 16, 2026

ahmedsameha1 commented on Jun 13, 2026

ahmedsameha1 commented on Jun 13, 2026

flutter-triage-bot commented on Jul 27, 2026

flutter-triage-bot commented on Aug 18, 2026

justinmc commented on Aug 18, 2026

ahmedsameha1 commented on Aug 19, 2026

justinmc commented on Aug 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions