1. 07 Jul, 2023 5 commits
  2. 06 Jul, 2023 6 commits
    • fzyzcjy's avatar
      Super tiny code optimization: No need to redundantly check whether value has changed (#130050) · bf72b635
      fzyzcjy authored
      Removed two unnecessary `if` conditions.
      bf72b635
    • Polina Cherkasova's avatar
    • Gil Nobrega's avatar
      [a11y] CupertinoSwitch On/Off labels (#127776) · 4f6c8877
      Gil Nobrega authored
      Adds optional visual labels to Cupertino's on/off switch for accessibility.
      4f6c8877
    • Henrique Nascimento's avatar
      Add option for flexible space on material SearchDelegate (#128132) · eebb1d6d
      Henrique Nascimento authored
      This pull request introduces the `buildFlexibleSpace` method to the `SearchDelegate` class in the material library. 
      It allows users to add a flexible space widget to the `AppBar` in a `_SearchPage`, providing more customization options.
      
      This PR does not fix any specific issue as there are no open issues related to this feature.
      eebb1d6d
    • luckysmg's avatar
      [framework] Add textField OCR support for framework side (#96637) · e0ad1296
      luckysmg authored
      iOS OCR keyboard input support.
      e0ad1296
    • Ian Hickson's avatar
      Allow long-press gestures to continue even if buttons change. (#127877) · bc49cd1b
      Ian Hickson authored
      Previously, if you changed buttons during a long-press gesture, if it was before the gesture was accepted we would discard it, and if it was after the gesture was accepted we would silently end it without firing any of the relevant events.
      
      This silent cancelation behavior is terrible because it means there's no way for consumers to know what state they're in, so you end up with widgets that thing they're still being long-pressed even though nothing is happening.
      
      We could change the behavior in three ways, as far as I can tell:
      
      - we could send a cancel event when you change buttons. This would introduce a new kind of transition (start->cancel) which I don't think we currently require people to support. This would therefore not fix existing code and would make future code more complicated to handle a really obscure user action that it seems unlikely anyone cares about.
      
      - we could send an end event when you change buttons. This would mean the action commits, even though the user is still holding the mouse button down. This seems slightly better than the previous option but still not ideal as it means nudging the mouse button commits you even though you're still holding the button down.
      
      - we could ignore button changes after the long-press has been accepted.
      
      I implemented the last one in this PR.
      bc49cd1b
  3. 05 Jul, 2023 4 commits
  4. 04 Jul, 2023 1 commit
  5. 01 Jul, 2023 1 commit
  6. 30 Jun, 2023 3 commits
  7. 28 Jun, 2023 5 commits
  8. 27 Jun, 2023 4 commits
  9. 26 Jun, 2023 1 commit
  10. 23 Jun, 2023 4 commits
  11. 22 Jun, 2023 6 commits