- 09 Mar, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 21 Feb, 2018 1 commit
-
-
amirh authored
* add a FAB NotchMaker to ScaffoldGeometry * add a notchMaker to FloatingActionButton * Initial implementation of BottomAppBar Mainly includes the notch making logic. Not yet tested as currently there is no way to make the FAB and the BAB overlap, once #14368 to lands we could add unit tests to the BottomAppBar as well. * use a closeable for clearing the FAB notchmaker
-
- 14 Feb, 2018 1 commit
-
-
amirh authored
-
- 13 Feb, 2018 1 commit
-
-
amirh authored
Adds a ScaffoldGeometry class and ValueNotifier for it. A scaffold's ScaffoldGeometry notifier is held in the _ScaffoldState, and is passed to _ScaffoldScope. New ScaffoldGemometry objects are built and published to the notifier.
-
- 07 Feb, 2018 1 commit
-
-
Chris Bracken authored
Applies left, right, and bottom media padding (e.g. iOS safe area insets) around ButtonBar in the material scaffold persistentFooterButtons.
-
- 02 Feb, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 01 Feb, 2018 1 commit
-
-
Chris Bracken authored
Note: also fixes a bug wherein bottom media padding was applied even in the presence of persistent footer buttons. The material spec states that the keyboard should be positioned on top of any bottom navigation bar or persistent footer buttons widget(s). We no longer inset the bottom of bottom navigation bars / persistent footer buttons by the bottom viewInset. Body content bottom (and the bottom of bottom sheets) is now determined by the greater of: 1. bottom view inset (the keyboard height) 2. bottom elements (nav bar, footer buttons) relative to the window max-Y.
-
- 11 Jan, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 08 Dec, 2017 1 commit
-
-
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
-
- 07 Dec, 2017 2 commits
-
-
Chris Bracken authored
This patch contains no framework changes. This change adjusts a test bottom navigation bar height to be greater than the media bottom padding. This change is pre-factoring to clarify diffs in an upcoming change that will expose bottom padding to the bottom navigation bar in order to allow it to visually adapt its appearance in the presence of bottom padding such as thatexposed for the iPhone X home screen indicator. Since the bottom padding was previously greater than the height of the bottom navigation bar, the height of insideBottomNavigation bar was driven to 0 when padding is exposed.
-
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).
-
- 02 Nov, 2017 2 commits
-
-
Adam Barth authored
-
5u3it authored
Adds `Scaffold#endDrawer` property to supply a second drawer to a Scaffold.
-
- 03 Oct, 2017 1 commit
-
-
Michael Goderbauer authored
* Drop invisible SemanticsNodes from tree A node is invisible if it is outside of the bounds of the screen and if it is not merged into its (partially) visible parent. Also in this PR: only set `wasAffectedByClip` to true if the nodes has actually been clipped. * Fix other failing tests * renaming * review feedback * more doc
-
- 29 Sep, 2017 1 commit
-
-
Ian Hickson authored
* SafeArea * AnimatedSafeArea * AppBar test * Apply feedback
-
- 31 Aug, 2017 1 commit
-
-
Alexandre Ardhuin authored
* upgrade to linter-0.1.35 * re-enable lint prefer_const_constructors * address review comments
-
- 30 Aug, 2017 1 commit
-
-
Adam Barth authored
Fixes #11369
-
- 06 Jul, 2017 1 commit
-
-
Michael Goderbauer authored
* Exclude modal barrier from semantics on Android * Add tests
-
- 03 Jun, 2017 1 commit
-
-
Michael Goderbauer authored
Adds a widgets that blocks all semantics of widgets below it in paint order within the same container (#10425)
-
- 27 Apr, 2017 2 commits
-
-
Ian Hickson authored
-
Ian Hickson authored
backgroundColor -> color backgroundImage -> image BackgroundImage -> DecorationImage
-
- 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
-
- 13 Apr, 2017 1 commit
-
-
Hans Muller authored
* Scaffold appBar is-a PreferredSizeWidget, etc * Updated * Updated per review feedback
-
- 12 Apr, 2017 1 commit
-
-
Ian Hickson authored
* Manually fix every use of Point.x and Point.y Some of these were moved to dx/dy, but not all. * Manually convert uses of the old gradient API * Remove old reference to Point. * Mechanical changes I applied the following at the root of the Flutter repository: git ls-files -z | xargs -0 sed -i 's/\bPoint[.]origin\b/Offset.zero/g' git ls-files -z | xargs -0 sed -i 's/\bPoint[.]lerp\b/Offset.lerp/g' git ls-files -z | xargs -0 sed -i 's/\bnew Point\b/new Offset/g' git ls-files -z | xargs -0 sed -i 's/\bconst Point\b/const Offset/g' git ls-files -z | xargs -0 sed -i 's/\bstatic Point /static Offset /g' git ls-files -z | xargs -0 sed -i 's/\bfinal Point /final Offset /g' git ls-files -z | xargs -0 sed -i 's/^\( *\)Point /\1Offset /g' git ls-files -z | xargs -0 sed -i 's/ui[.]Point\b/ui.Offset/g' git ls-files -z | xargs -0 sed -i 's/(Point\b/(Offset/g' git ls-files -z | xargs -0 sed -i 's/\([[{,]\) Point\b/\1 Offset/g' git ls-files -z | xargs -0 sed -i 's/@required Point\b/@required Offset/g' git ls-files -z | xargs -0 sed -i 's/<Point>/<Offset>/g' git ls-files -z | xargs -0 sed -i 's/[.]toOffset()//g' git ls-files -z | xargs -0 sed -i 's/[.]toPoint()//g' git ls-files -z | xargs -0 sed -i 's/\bshow Point, /show /g' git ls-files -z | xargs -0 sed -i 's/\bshow Point;/show Offset;/g' * Mechanical changes - dartdocs I applied the following at the root of the Flutter repository: git ls-files -z | xargs -0 sed -i 's/\ba \[Point\]/an [Offset]/g' git ls-files -z | xargs -0 sed -i 's/\[Point\]/[Offset]/g' * Further improvements and a test * Fix minor errors from rebasing... * Roll engine
-
- 10 Apr, 2017 2 commits
- 07 Apr, 2017 1 commit
-
-
Ian Hickson authored
Aggressively apply the const lint.
-
- 14 Mar, 2017 1 commit
-
-
Adam Barth authored
The new name follows the pattern of the name suggesting which layout protocol the parent expects the child to speak. Fixes #8664
-
- 13 Mar, 2017 1 commit
-
-
Ian Hickson authored
-
- 08 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
* prefer const constructors * fix double throw
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 01 Mar, 2017 1 commit
-
-
Chris Bracken authored
This ensures that both timer/microtask queues are cleared out rather than assuming that all work is completed in a specified amount of time.
-
- 26 Feb, 2017 1 commit
-
-
Adam Barth authored
Fixes #8413
-
- 24 Feb, 2017 1 commit
-
-
Adam Barth authored
It's common to just want a simple colored box. Simple thing should be simple, so this patch adds a convenience argument to Continer for creating a box decoration that is just a color. Fixes #5555
-
- 17 Feb, 2017 2 commits
-
-
Adam Barth authored
Rename all the "2" classes related to scrolling to remove the "2". Now that the old scrolling code is gone, we don't need to use the suffix.
-
Adam Barth authored
All the clients have migrated to Scrollable2.
-
- 09 Feb, 2017 2 commits
-
-
Alexandre Ardhuin authored
-
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.
-
- 01 Feb, 2017 1 commit
-
-
Adam Barth authored
This patch removes unnecessary uses of scrollableKey from tests. Scrollable2 will likely use a different mechanism for identifying itself, so we want to focus on the uses of scrollableKey that will need to be addressed in the new implementation.
-