1. 25 Mar, 2021 1 commit
  2. 23 Mar, 2021 1 commit
  3. 02 Mar, 2021 1 commit
  4. 16 Feb, 2021 1 commit
  5. 23 Jan, 2021 1 commit
  6. 25 Nov, 2020 1 commit
  7. 20 Nov, 2020 1 commit
  8. 12 Nov, 2020 1 commit
  9. 26 Oct, 2020 1 commit
  10. 21 Oct, 2020 1 commit
  11. 09 Oct, 2020 1 commit
  12. 08 Oct, 2020 1 commit
  13. 27 Sep, 2020 1 commit
  14. 31 Aug, 2020 1 commit
    • Chris Bracken's avatar
      Prefer moreOrLessEquals over closeTo (#64915) · c0ea00ed
      Chris Bracken authored
      Flutter's `moreOrLessEquals` has a few advantages over `closeTo` from
      the `matcher` package:
      
         * It emits the epsilon value in the test result on failure.
         * It uses a named parameter for epsilon, which improves readability
           at the call site.
         * It has a reasonable default for epsilon in cases where something
           more specific isn't required.
      
      Using it also has the nice property that it aids in its own discovery
      when when people go looking for such functionality in new tests.
      
      This change also includes a couple unrelated whitespace formatting cleanups.
      c0ea00ed
  15. 08 Aug, 2020 1 commit
  16. 05 Aug, 2020 1 commit
  17. 28 Jul, 2020 1 commit
  18. 23 Jul, 2020 1 commit
  19. 16 Jul, 2020 1 commit
    • Todd Volkert's avatar
      Allow transparent barrierColor in showDialog methods (#61516) · e2cdc9f9
      Todd Volkert authored
      `showDialog()` and `showGeneralDialog()` were allowing transparent
      colors but then triggering an assertion down the stack while building
      the modal barrier. The assertion existed to keep from animating from
      transparent to transparent, but there's no need for the assertion,
      since we can just treat the transparent case as the same as the null
      case -- no animation necessary.
      e2cdc9f9
  20. 15 Jul, 2020 1 commit
    • Todd Volkert's avatar
      Add defaults to `showGeneralDialog()` (#61503) · 0d2421d5
      Todd Volkert authored
      The function passes most of its arguments through to
      `_DialogRoute`, but it wasn't providing the default
      values that `_DialogRoute` was, causing it to override
      the defaults will null values.
      0d2421d5
  21. 25 Jun, 2020 1 commit
  22. 24 Jun, 2020 1 commit
  23. 18 Jun, 2020 1 commit
  24. 11 Jun, 2020 2 commits
  25. 23 Mar, 2020 1 commit
  26. 27 Feb, 2020 1 commit
    • Greg Spencer's avatar
      Change Focus.unfocus to take a disposition for where the focus… (#50831) · d4226566
      Greg Spencer authored
      When Focus.unfocus is called, the caller usually just thinks about wanting to remove focus from the node, but really, unfocus is a request to automatically pass the focus to another (hopefully useful) node.
      
      This PR removes the focusPrevious flag from unfocus, and replaces it with a disposition enum that indicates where the focus should go from here.
      
      The other value of the UnfocusDisposition enum is UnfocusDisposition.scope.
      
      UnfocusDisposition.previouslyFocusedChild is closest to what focusPrevious used to do: focus the nearest enclosing scope and use its focusedChild field to walk down the tree, finding the leaf focusedChild. This PR modifies it slightly so that it walks up to the nearest focusable enclosing scope before trying to focus the children. This change addresses #48903
      
      A new mode: UnfocusDisposition.scope will focus the nearest focusable enclosing scope of this node without trying to use the FocusScopeNode.focusedChild value to descend to the leaf focused child. This is useful as a default for both text field finalization and for what happens when canRequestFocus is set to false. It allows the scope to stay focused so that nextFocus/previousFocus still work as expected, but removes the focus from primary focus.
      
      In addition to those changes, unfocus called on a FocuScope that wasn't the primary focus used to unfocus the primary focus instead. I removed that behavior, since it was buggy: if the primary focus was inside of a child scope, and you called unfocus on the parent scope, then the child scope could have focused another of its children instead, leaving the scope that you called unfocus on with hasFocus returning true still. If you want to remove the focus from the primary focus instead of the scope, that's easy enough to do: just call primaryFocus.unfocus().
      
      Fixes #48903
      d4226566
  27. 05 Feb, 2020 1 commit
  28. 30 Jan, 2020 1 commit
    • chunhtai's avatar
      Fix focus when popping pages (#49714) · 406d8f7f
      chunhtai authored
      Fixes the focus handling when popping pages so that when multiple pages are popped, the focus doesn't try to focus the interstitial pages.
      406d8f7f
  29. 29 Jan, 2020 1 commit
  30. 27 Jan, 2020 1 commit
  31. 17 Jan, 2020 1 commit
  32. 16 Jan, 2020 2 commits
  33. 10 Jan, 2020 1 commit
  34. 09 Jan, 2020 1 commit
  35. 07 Jan, 2020 1 commit
  36. 16 Dec, 2019 1 commit
  37. 27 Nov, 2019 1 commit
    • Ian Hickson's avatar
      License update (#45373) · 449f4a66
      Ian Hickson authored
      * Update project.pbxproj files to say Flutter rather than Chromium
      
      Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright.
      
      * Update the copyright notice checker to require a standard notice on all files
      
      * Update copyrights on Dart files. (This was a mechanical commit.)
      
      * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine.
      
      Some were already marked "The Flutter Authors", not clear why. Their
      dates have been normalized. Some were missing the blank line after the
      license. Some were randomly different in trivial ways for no apparent
      reason (e.g. missing the trailing period).
      
      * Clean up the copyrights in non-Dart files. (Manual edits.)
      
      Also, make sure templates don't have copyrights.
      
      * Fix some more ORGANIZATIONNAMEs
      449f4a66
  38. 01 Nov, 2019 1 commit