1. 17 Oct, 2018 1 commit
  2. 05 Oct, 2018 2 commits
  3. 14 Sep, 2018 1 commit
  4. 13 Sep, 2018 1 commit
  5. 12 Sep, 2018 1 commit
  6. 07 Sep, 2018 1 commit
  7. 04 Sep, 2018 2 commits
  8. 09 Aug, 2018 1 commit
  9. 03 Aug, 2018 1 commit
    • liyuqian's avatar
      Add Clip enum to Material and related widgets (#18576) · 9ffa1c51
      liyuqian authored
      See details in our proposal for this breaking API change and #18057. This PR setup all code paths to allow the change but doesn't change the clip behavior by itself. We'll change `defaultClipBehavior` from `Clip.antiAlias` to `Clip.none` in the following PR to change the clip behavior and update tests.
      9ffa1c51
  10. 31 Jul, 2018 1 commit
  11. 11 Jul, 2018 1 commit
  12. 21 Jun, 2018 2 commits
  13. 14 Jun, 2018 1 commit
  14. 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
  15. 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
  16. 07 Jun, 2018 1 commit
  17. 05 Jun, 2018 2 commits
  18. 30 May, 2018 2 commits
  19. 26 May, 2018 1 commit
  20. 04 May, 2018 1 commit
  21. 03 May, 2018 2 commits
  22. 20 Mar, 2018 1 commit
  23. 12 Mar, 2018 1 commit
  24. 09 Mar, 2018 1 commit
  25. 28 Feb, 2018 1 commit
  26. 06 Feb, 2018 2 commits
    • Greg Spencer's avatar
      Adds the semantic node traversal API. (#14060) · 14309b93
      Greg Spencer authored
      This adds an API for defining the semantic node traversal order.
      
      It adds a sortOrder argument to the Semantics widget, which is a class that can define a list of sort keys to sort on. The keys are sorted globally so that an order that doesn't have to do with the current widget hierarchy may be defined.
      
      It also adds a shortcut sortKey argument to the Semantics widget that simply sets the sortOrder to just contain that key.
      
      The platform side (flutter/engine#4540) gets an additional member in the SemanticsData object that is an integer describing where in the overall order each semantics node belongs. There is an associated engine-side change that takes this integer and uses it to order widgets for the platform's accessibility services.
      14309b93
    • Alexandre Ardhuin's avatar
      unnessary parenthesis (#14475) · 2e80bf1d
      Alexandre Ardhuin authored
      2e80bf1d
  27. 02 Feb, 2018 1 commit
  28. 18 Jan, 2018 1 commit
  29. 10 Jan, 2018 1 commit
  30. 09 Jan, 2018 2 commits
  31. 22 Dec, 2017 1 commit
    • Michael Goderbauer's avatar
      Fixes crash caused by invisible semantics children (#13740) · 4e13cd07
      Michael Goderbauer authored
      **tl;dr:** A `RenderObject` can only be an effective semantics boundary if it actually owned a `SemanticsNode` in the previous tree generation.
      
      When using the `BlockSemantics` widget it is possible to introduce `RenderObject`s that are configured to be a semantics boundary, but because their semantics are blocked by `BlockSemantics` they will not (immediately) end up owning a `SemanticsNode`. When now a descendant of such a node-less semantics boundary marks itself as needing a semantics update we walk up the tree until we find the closest semantics boundary (which is our node-less `RenderObject`). We now incorrectly assume that this semantics boundary has a valid `SemanticsNode` and only regenerate the semantics subtree below this node. However, because the identified semantics boundary doesn't actually own a valid `SemanticsNode` asserts are throwing (e.g. `Child with id xx is invisible and should not be added to tree.`).
      
      To fix this problem, we can just abort the walk if we reach a semantics boundary without a semantics node because (for now) we know that the semantics information of this branch will not make it into the final semantics tree.
      If the semantics block is ever removed, the current algorithm re-generates the semantics for the entire branch and the semantics will be up-to-date then despite the abort. I've added a test to verify this to make sure it continues to work even when we change the algorithm.
      
      Fixes https://github.com/flutter/flutter/issues/13326.
      /cc @gavindoughtie FYI
      4e13cd07
  32. 21 Dec, 2017 1 commit