1. 09 Apr, 2020 1 commit
  2. 08 Apr, 2020 6 commits
  3. 07 Apr, 2020 3 commits
  4. 06 Apr, 2020 1 commit
  5. 05 Apr, 2020 1 commit
  6. 03 Apr, 2020 3 commits
  7. 02 Apr, 2020 1 commit
  8. 01 Apr, 2020 2 commits
    • Roger Yang's avatar
      7a616c9e
    • Mugurell's avatar
      For #3182 - Separate behaviours depending on user's MotionEvents · 5d58e943
      Mugurell authored
      There are currently 3 Views interested in handling user's MotionEvents:
      - GeckoView which renders web content
      - SwipeRefreshLayout which handles pull down to refresh
      - BrowserToolbar which can be dynamically hidden
      
      Each of them have different behaviours based on different conditions so I
      - removed the coupling of BrowserToolbar and Geckoview from `NestedGeckoView`.
      It's `onTouchEventForResult` will now only set behaviour for GeckoView.
      - created a new EngineView enum to expose the `PanZoomController` possible
      result of how a specific user touch was handled to any components that have a
      reference to an instance of EngineView without the need to have
      `concept-engine` as a dependency.
      - implemented specific behaviour in `SwipeRefreshFeature` for the pull down to
      refresh functionality and in the `BrowserToolbarBottomBehavior` for the dynamic
      navigation bar functionality.
      
      Mapped PanZoomController's INPUT_RESULT to a new enum in order to not enforce
      the need of including geckoview as a dependency in all components interested in
      how a user's `MotionEvent` was handled and also because webview doesn't expose
      such values so we needed a wrapper for it's handled or not boolean return.
      5d58e943
  9. 31 Mar, 2020 3 commits
  10. 30 Mar, 2020 1 commit
  11. 27 Mar, 2020 1 commit
  12. 26 Mar, 2020 4 commits
  13. 23 Mar, 2020 4 commits
  14. 20 Mar, 2020 2 commits
  15. 18 Mar, 2020 1 commit
  16. 17 Mar, 2020 4 commits
  17. 13 Mar, 2020 1 commit
  18. 11 Mar, 2020 1 commit