Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workaround for Drawer.initState() fails #716

Merged
merged 1 commit into from
Aug 20, 2015
Merged

Workaround for Drawer.initState() fails #716

merged 1 commit into from
Aug 20, 2015

Conversation

HansMuller
Copy link

This is a hack to avoid #715

In theory, the navigator's state should be updated in the event handler that triggers opening the drawer. It's not obvious how to do this, since we only build the Drawer when it's supposed to be visible (and once we're building it's too late). Perhaps responsibility needs to be borne by the StockHome class?

@mpcomplete
Copy link
Contributor

As far as Drawer ignoring the showing flag, Drawer should probably follow the way PopupMenu handles this. But we still might need the scheduleMicrotask either way, so LGTM.

HansMuller pushed a commit that referenced this pull request Aug 20, 2015
Workaround for Drawer.initState() fails

This is a hack to avoid #715

In theory, the navigator's state should be updated in the event handler that triggers opening the drawer. It's not obvious how to do this, since we only build the Drawer when it's supposed to be visible (and once we're building it's too late).
@HansMuller HansMuller merged commit a5579f2 into flutter:master Aug 20, 2015
@HansMuller HansMuller deleted the drawer-bug branch August 20, 2015 18:54
@Hixie
Copy link
Contributor

Hixie commented Aug 20, 2015

IMHO we should fix this correctly now, not check in workarounds. Otherwise we're just digging ourselves into technical debt.

@HansMuller
Copy link
Author

I will make a proposal for a better fix.

@Hixie
Copy link
Contributor

Hixie commented Sep 9, 2015

I just tripped over this technical debt. I think it may be implicated in the weird assertions we've been getting. This is why I didn't want us to check in a workaround.

rhencke pushed a commit to rhencke/engine that referenced this pull request Dec 20, 2020
Use Stdout.terminalColumns for line length

Fall back on a 200-character default, which is less likely to obscure
test names when printing to a non-terminal destination.

Closes flutter#86
aam added a commit to aam/engine that referenced this pull request Apr 18, 2023
Changes since last roll:
```
059d155 [dart] Add identifier needed for zlib roll (flutter#718)
459d3e5 Bump github/codeql-action from 2.2.11 to 2.2.12 (flutter#716)
91f1ba5 Bump actions/checkout from 3.5.1 to 3.5.2 (#715)
2e5c483 Bump actions/checkout from 3.5.0 to 3.5.1 (flutter#714)
a5af13d Remove codeql. (flutter#713)
```
auto-submit bot pushed a commit that referenced this pull request Apr 18, 2023
Changes since last roll:
```
059d155 [dart] Add identifier needed for zlib roll (#718)
459d3e5 Bump github/codeql-action from 2.2.11 to 2.2.12 (#716)
91f1ba5 Bump actions/checkout from 3.5.1 to 3.5.2 (#715)
2e5c483 Bump actions/checkout from 3.5.0 to 3.5.1 (#714)
a5af13d Remove codeql. (#713)
```
itekdev pushed a commit to itekdev/flutter-engine0 that referenced this pull request May 1, 2023
Bump github/codeql-action from 2.2.11 to 2.2.12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants