1. 13 Jul, 2021 1 commit
  2. 23 Jun, 2021 1 commit
  3. 09 Jun, 2021 1 commit
  4. 04 Jun, 2021 1 commit
  5. 28 Apr, 2021 1 commit
  6. 11 Mar, 2021 1 commit
    • Justin McCandless's avatar
      Text Editing Movement Keys via Shortcuts (#75032) · 541bff40
      Justin McCandless authored
      Text editing shortcuts involving the arrow keys are no longer handled by RenderEditable's RawKeyboardListener, they use the new Shortcuts setup.  First PR in a plan to port all text editing keyboard handling to shortcuts.
      541bff40
  7. 20 Nov, 2020 1 commit
  8. 17 Nov, 2020 1 commit
  9. 16 Nov, 2020 1 commit
  10. 12 Nov, 2020 2 commits
  11. 11 Nov, 2020 1 commit
  12. 07 Oct, 2020 2 commits
  13. 05 Oct, 2020 1 commit
  14. 02 Oct, 2020 1 commit
  15. 10 Sep, 2020 1 commit
  16. 08 Sep, 2020 1 commit
  17. 04 Sep, 2020 1 commit
  18. 03 Sep, 2020 1 commit
  19. 24 Jun, 2020 1 commit
  20. 18 Jun, 2020 1 commit
  21. 12 Jun, 2020 1 commit
  22. 11 Jun, 2020 1 commit
  23. 08 Jun, 2020 1 commit
  24. 07 Apr, 2020 1 commit
    • Greg Spencer's avatar
      Revise Action API (#42940) · 0f68b46f
      Greg Spencer authored
      This updates the Action API in accordance with the design doc for the changes: flutter.dev/go/actions-and-shortcuts-design-revision
      
      Fixes #53276
      0f68b46f
  25. 23 Feb, 2020 1 commit
  26. 13 Feb, 2020 1 commit
    • Greg Spencer's avatar
      Reland: Add OrderedFocusTraversalPolicy and FocusTraversalGrou… (#50672) · d57d4935
      Greg Spencer authored
      This re-lands #49235 with the addition of includeSemantics flag on the Focus widget so that the FocusTraversalGroup can create a Focus widget without affecting the semantics tree.
      
      The FocusTraversalGroup uses the Focus widget to create a grouping of descendants for traversal, but doesn't actually participate in focus (canRequestFocus is always false), so we don't want it to add a Semantics widget in that case, since that can cause semantics changes. The canRequestFocus attribute can also be used when a widget is disabled, so we do sometimes want to include Semantics even if that is false, but not in the case where it is always false, as for FocusTraversalGroup.
      
      - Added a test to make sure that FocusTraversalGroup doesn't add any semantics information.
      d57d4935
  27. 12 Feb, 2020 1 commit
  28. 11 Feb, 2020 2 commits
    • Alexandre Ardhuin's avatar
      f15c887c
    • Greg Spencer's avatar
      Add OrderedFocusTraversalPolicy and FocusTraversalGroup to all… (#49235) · 8ef5e2f0
      Greg Spencer authored
      This change adds a way to provide explicit focus order for a part of the widget tree.
      
      It adds FocusTraversalPolicyGroup, which in many ways is similar to DefaultFocusTraversal, except that it groups a widget subtree together so that those nodes are traversed as a group. DefaultFocusTraversal doesn't work as one would expect: If there is more than one DefaultFocusTraversal inside of a focus scope, the policy can change depending on which node was asked to move "next", which can cause unexpected behavior. The new grouping mechanism doesn't have that problem. I deprecate DefaultFocusTraversal in this PR.
      
      It also adds OrderedFocusTraversalPolicy, which is a policy that can be supplied to FocusTraversalPolicyGroup to set the policy for a sub-tree. It looks for FocusTraversalOrder inherited widgets, which use a FocusOrder to do the sorting. FocusOrder has two subclasses: NumericalFocusOrder (which sorts based on a double), and LexicalFocusOrder, which sorts based on a String.
      
      As part of doing this, I refactored the way FocusTraversalPolicy is implemented so that it has more default implementation methods, and exposes a new protected member: sortDescendants, which makes it easier for developers to make their own policy subclasses: they only need to implement sortDescendants to get a new ordering behavior, but can also still override any of the default implementation behaviors if they need different behavior.
      
      I was able to do this without breaking the API (AFAICT).
      8ef5e2f0
  29. 08 Feb, 2020 1 commit
  30. 28 Jan, 2020 1 commit
  31. 27 Jan, 2020 1 commit
  32. 23 Jan, 2020 1 commit
  33. 22 Jan, 2020 2 commits
  34. 17 Jan, 2020 1 commit
  35. 16 Jan, 2020 1 commit
  36. 16 Dec, 2019 1 commit