1. 09 Jan, 2019 1 commit
  2. 08 Jan, 2019 2 commits
  3. 07 Jan, 2019 1 commit
  4. 04 Jan, 2019 1 commit
  5. 12 Dec, 2018 1 commit
  6. 07 Nov, 2018 1 commit
    • Michael Beckler's avatar
      BottomNavigationBar: bug fix for dealing with animations with shifting tabs (#22264) · 9abce96e
      Michael Beckler authored
      Should fix #22226.
      
      Code introduced in #20890 caused a regression that broke color flooding animations in a BottomNavigationBar that has BottomNavigationBarType.shifting.
      
      The original issue (#19653) dealt with background color changes not occurring until another tab was selected. The result is that the background color instantly changes whenever the state changes and when the widget changes, instead of allowing a new widget to animate the background color change.
      9abce96e
  7. 06 Nov, 2018 1 commit
  8. 16 Oct, 2018 1 commit
  9. 10 Oct, 2018 1 commit
  10. 08 Oct, 2018 2 commits
  11. 02 Oct, 2018 1 commit
  12. 01 Oct, 2018 1 commit
  13. 28 Sep, 2018 1 commit
  14. 23 Sep, 2018 1 commit
  15. 14 Sep, 2018 1 commit
  16. 12 Sep, 2018 2 commits
  17. 28 Aug, 2018 1 commit
  18. 23 Aug, 2018 1 commit
  19. 22 Aug, 2018 1 commit
    • Will Larche's avatar
      [Gallery] Material elevations (shadows) demo (#20842) · 47cffd16
      Will Larche authored
      * [Gallery] Elevations demo. TODO: Correct icon.
      
      * [Gallery] More elevations for the elevation demo.
      
      * [Gallery] Elevation toggle for elevation demo.
      
      * [Demos] Update temp icon on elevations demo.
      
      * [Demos] Changing action icon.
      
      * [Demos] Same.
      
      * [Demos] Adding new and const.
      
      * [Demos] Reverting formatting.
      
      * [Gallery] PR Feedback.
      47cffd16
  20. 18 Aug, 2018 1 commit
    • Ian Hickson's avatar
      Fixes resulting from audit of issues links (#20772) · 8c79f40d
      Ian Hickson authored
      * Fixes resulting from audit of issues links
      
      I looked at every link to GitHub in our repo. For cases where we had a TODO that was waiting for a bug to be fixed, and the bug has now been fixed, I applied the pending change. For cases where the link was out of date, I updated the link.
      
      * Update run_test.dart
      
      skip this test again since it failed on linux and macos bots
      8c79f40d
  21. 16 Aug, 2018 2 commits
  22. 04 Aug, 2018 1 commit
  23. 02 Aug, 2018 1 commit
  24. 30 Jul, 2018 2 commits
  25. 27 Jul, 2018 1 commit
  26. 23 Jul, 2018 1 commit
  27. 20 Jul, 2018 2 commits
  28. 16 Jul, 2018 2 commits
  29. 21 Jun, 2018 1 commit
    • amirh's avatar
      Move the notch computation from the FAB to the BAB. (#18372) · c39f2f26
      amirh authored
      Move the notch computation from the FAB to the BAB.
      
      The notch in the BAB (bottom action bar) for the FAB (floating action button) was previously kept as part of the FAB's implementation. This was done to keep the shape of the FAB and the shape of the notch coupled.
      That approach resulted in a somewhat complex and 'non Fluttery' mechanism for propagating the notch computation from the FAB to the BAB.
      
      This CL uncouples the FAB and the notch computation.
      With the new API the BAB computes its overall shape including the notch using a NotchedShape delegate.
      
      This includes multiple breaking changes:
        * Scaffold.setFloatingActionButtonNotchFor is deleted.
        * The ComputeNotch type is deleted.
        * The hasNotch property of BottomAppBar is deleted.
        * The notchMargin property of FloatingActionButton is deleted.
      
      Quick migration guide from the previous API:
      
      | Previous API | New API |
      | ------------------|-------------|
      | BottomAppBar(hasNotch: false) | BottomAppBar() |
      | Using a FloatingActionButton with: BottomAppBar() / BottomAppBar(hasNotch: true) | BottomAppBar(shape: CircularNotchedRectangle()) |
      | Scaffold.setFloatingActionButtonNotchFor(..) | No longer supported |
      c39f2f26
  30. 19 Jun, 2018 1 commit
  31. 13 Jun, 2018 1 commit
    • Chris Bracken's avatar
      Revert elimination of Dart 1 (#18460) · 2ae48845
      Chris Bracken authored
      fuchsia_tester.dart still assumes Dart 1. Previously, it ran tests directly
      from source, flutter_platform.dart automatically runs a kernel compile when
      operating in Dart 2 mode, but this assumes a functional Dart SDK is available
      in the artifacts directly, and fuchsia_tester.dart mocks out the artifacts
      directory with an empty temp dir.
      
      Remaining work is:
      1. Get the frontend server building as a dependency on Fuchsia.
      2. Patch fuchsia_tester.dart to use a valid Dart SDK and frontend server.
      
      This also reverts migration to Dart 2 typedef syntax.
      
      This reverts commit 6c56bb24. (#18362)
      This reverts commit 3daebd05. (#18316)
      2ae48845
  32. 11 Jun, 2018 1 commit
    • Greg Spencer's avatar
      Update typedef syntax to use Function notation and turn on lint for old notation. (#18362) · 6c56bb24
      Greg Spencer authored
      Now that Dart 1 is turned off, reapplying my change to turn on the prefer_generic_function_type_aliases analysis option, and fix all the typedefs to Dart 2 preferred syntax.
      
      Also eliminated the unused analysis_options_repo.yaml file and turned on public_member_api_docs in analysys_options.yaml.
      
      No logic changes, just changing the typedef syntax for all typedefs, and updating analysis options.
      6c56bb24
  33. 10 Jun, 2018 1 commit