- 16 Dec, 2017 1 commit
-
-
Chris Bracken authored
Applies any additional bottom, left, and right media padding inside the snackbar, if present. This accounts for the iPhone X home indicator widget and horizontal padding for the sensor housing notch in landscape orientation.
-
- 08 Dec, 2017 2 commits
-
-
Chris Bracken authored
Now that keyboard height is modelled as a (bottom) view inset, migrate scaffold bottom resizing to use view insets instead of bottom padding, which, after an engine roll, will only be used for safe areas. Until the aforementioned engine roll, the keyboard height is still included in both bottom padding and view insets. As such resizeToAvoidBottomPadding still drives bottom padding removal until that roll lands. Renames _ScaffoldLayout.bottomPadding to bottomViewInset
-
Chris Bracken authored
Also adds a TODO that should have landed with flutter/flutter#13423.
-
- 07 Dec, 2017 1 commit
-
-
Chris Bracken authored
Scaffold bottom padding now applies the maximum of window viewInsets.bottom (typically used for iOS safe areas) and padding.bottom (typically used for keyboard height).
-
- 04 Dec, 2017 1 commit
-
-
Ian Hickson authored
Also, extra docs. Fixes https://github.com/flutter/flutter/issues/13279 Fixes https://github.com/flutter/flutter/issues/2115
-
- 17 Nov, 2017 1 commit
-
-
Greg Spencer authored
I got tired of drive-by spelling fixes, so I figured I'd just take care of them all at once. This only corrects errors in the dartdocs, not regular comments, and I skipped any sample code in the dartdocs. It doesn't touch any identifiers in the dartdocs either. No code changes, just comments.
-
- 02 Nov, 2017 1 commit
-
-
5u3it authored
Adds `Scaffold#endDrawer` property to supply a second drawer to a Scaffold.
-
- 02 Oct, 2017 1 commit
-
-
Adam Barth authored
Unlike FractionalOffset, Alignment uses the center as the zero of the coordinate system, which makes the RTL math work out much cleaner. Also, make FractionalOffset into a subclass of Alignment so that clients can continue to use FractionalOffset.
-
- 29 Sep, 2017 1 commit
-
-
Ian Hickson authored
* SafeArea * AnimatedSafeArea * AppBar test * Apply feedback
-
- 11 Sep, 2017 1 commit
-
-
Adam Barth authored
Fix a bunch of obvious RTL bugs from code inspection.
-
- 30 Aug, 2017 1 commit
-
-
Adam Barth authored
Fixes #11369
-
- 29 Aug, 2017 1 commit
-
-
Mehmet Fidanboylu authored
* Notify the completer after the close animation completes on the snackbar * Review comments * Fix tests and analyzer warnings * Fix analyzer warnings
-
- 07 Aug, 2017 1 commit
-
-
Ian Hickson authored
-
- 08 Jun, 2017 1 commit
-
-
Ian Hickson authored
-
- 06 Jun, 2017 1 commit
-
-
Michael Goderbauer authored
It's redundant as iOS accessibility automatically includes this action on the clock in the status bar.
-
- 05 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 27 Apr, 2017 1 commit
-
-
Ian Hickson authored
-
- 23 Apr, 2017 1 commit
-
-
Alexandre Ardhuin authored
* more widget const constructors * prefer const constructors * address review comments
-
- 21 Apr, 2017 1 commit
-
-
Alexandre Ardhuin authored
* make @immutable const * fix build
-
- 17 Apr, 2017 1 commit
-
-
Hans Muller authored
-
- 15 Apr, 2017 1 commit
-
-
Ian Hickson authored
With this patch, you can do: ```dart Future<Null> foo() async { try { await controller.forward().orCancel; await controller.reverse().orCancel; await controller.forward().orCancel; } on TickerCanceled { // did not complete } } ``` ...in a State's async method, and so long as you dispose of the controller properly in your dispose, you'll have a nice way of doing animations in sequence without leaking the controller. try/finally works as well, if you need to allocate resources and discard them when canceled. Simultaneously, you can do: ```dart Future<Null> foo() async { await controller.forward().orCancel; await controller.reverse().orCancel; await controller.forward().orCancel; } ``` ...and have the same effect, where the method will just silently hang (and get GC'ed) if the widget is disposed, without leaking anything, if you don't need to catch the controller being killed. And all this, without spurious errors for uncaught exceptions on controllers.
-
- 13 Apr, 2017 1 commit
-
-
Hans Muller authored
* Scaffold appBar is-a PreferredSizeWidget, etc * Updated * Updated per review feedback
-
- 11 Apr, 2017 1 commit
-
-
xster authored
Rename State.config to State.widget Rename State.didUpdateConfig to State.didUpdateWidget Renamed all State subclasses' local variables named config to something else
-
- 29 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 15 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 08 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
Covers lib/ in package:flutter.
-
- 26 Feb, 2017 1 commit
-
-
Adam Barth authored
Fixes #8413
-
- 18 Feb, 2017 1 commit
-
-
Adam Barth authored
-
- 09 Feb, 2017 1 commit
-
-
Ian Hickson authored
Move the back button and drawer opening logic into the app bar. Move the tap-status-bar-to-scroll-to-top logic to using ScrollControllers. Provide a PrimaryScrollController and a `primary` flag on scroll views. Make it possible to track when a route becomes or stops being poppable.
-
- 04 Feb, 2017 1 commit
-
-
Ian Hickson authored
-
- 31 Jan, 2017 1 commit
-
-
Ian Hickson authored
-
- 22 Jan, 2017 1 commit
-
-
Ian Hickson authored
-
- 18 Jan, 2017 1 commit
-
-
Hans Muller authored
-
- 05 Jan, 2017 2 commits
-
-
Seth Ladd authored
Closes https://github.com/flutter/flutter/issues/6907
-
Adam Barth authored
The docs now include all the information contained in the exception. Fixes #6994
-
- 09 Dec, 2016 1 commit
-
-
Alexandre Ardhuin authored
-
- 30 Nov, 2016 2 commits
-
-
Hans Muller authored
-
Adam Barth authored
Fixes #6915
-
- 23 Nov, 2016 1 commit
-
-
Hans Muller authored
-