1. 31 Oct, 2019 1 commit
  2. 24 Oct, 2019 1 commit
  3. 17 Oct, 2019 1 commit
  4. 12 Oct, 2019 1 commit
    • Lina Cambridge's avatar
      Pass redirect source and target flags to history tracking delegates. · 15b873fe
      Lina Cambridge authored
      There's some confusion in `GeckoEngineSession` about redirect flags.
      The `VISIT_REDIRECT_SOURCE` and `VISIT_REDIRECT_SOURCE_PERMANENT` flags
      that we get from GeckoView's history delegate are for the redirect
      _source_, not the visit type. They indicate if the URL passed to
      `onVisited` is redirecting _to_ another URL, most likely because the
      server returned an HTTP 3xy status code with a `Location` header.
      Rust Places decides whether to mark the URL as hidden based on
      these flags.
      
      `VISIT_REDIRECT_{PERMANENT, TEMPORARY}`, however, indicate if the
      URL passed to `onVisited` is the _target_ of a redirect (in other
      words, the page that's _in_ the `Location` header). These get
      translated into `VisitType` flags, which Rust Places stores as the
      visit transition type. These two flags don't affect whether a URL
      is hidden.
      
      Note that, in a redirect chain, the middle links are both sources and
      targets. For example, in "mozilla.org" -> "www.mozilla.org" ->
      "www.mozilla.org/en-US", "www.mozilla.org" is both a redirect target
      (since "mozilla.org" redirected to it), and a source (it redirected
      to "www.mozilla.org/en-US").
      
      See mozilla-mobile/fenix#3526.
      15b873fe
  5. 07 Oct, 2019 1 commit
  6. 02 Oct, 2019 1 commit
  7. 10 Sep, 2019 1 commit
  8. 03 Sep, 2019 1 commit
  9. 14 Aug, 2019 2 commits
  10. 08 Aug, 2019 1 commit
  11. 02 Aug, 2019 1 commit
  12. 23 Jul, 2019 1 commit
  13. 19 Jul, 2019 2 commits
  14. 12 Jul, 2019 1 commit
  15. 01 Jul, 2019 1 commit
  16. 07 Jun, 2019 1 commit
  17. 04 Jun, 2019 1 commit
  18. 03 Jun, 2019 1 commit
  19. 31 May, 2019 1 commit
  20. 30 May, 2019 1 commit
    • James Hugman's avatar
      Fixes #2976 Introduce feature-app-links · f0eb46fc
      James Hugman authored
      This includes UI in private tabs.
      
      Squashed commits:
      [180e515e8] Connect to Session Observer and thence to AppLinksFeature.
      [77922dcc0] browser-engine-system tests passing
      [045717868] lint etc
      [6f7b44cad] Thread another Boolean through EngineObserver -> Session onLoadRequest
      [18693cad0] Start testing the feature.
      [5e0a93556] Fixup tests to use shadow package manager, and catch some new bugs.
      [3a5976dde] Split use cases up for menu and intercepting cases.
      [f7eae96dd] Address reviewer comments re: dead code and docs
      [b15ffb88c] Rename triggeredByUserInteraction to loadRequestTriggeredByUserInteraction
      [edc49b573] Move session observer into member of feature
      [91ed1f5ac] Add changelog entry
      [098dc5067] Add boolean flag to prevent interception of links
      [f92731a44] Add load request/trigger by user interaction to session.observer
      [46385577d] Move opening to another use case, with test
      [56da7e7c1] Change into using feature
      [643c9f453] Remove duplicate copyright
      [6b3f80bbc] Add testing of get and a fragment for open use cases
      [669c84567] Add AppLinksRedirectConfig and supporting use cases.
      
      There is a url redirect creation use case, a load URL use case and an interceptor.
      [72896a567] AppLinksUseCases detects if a URL can be opened with another non-browser app
      [939eb62fa] Initial commit of empty feature-app-links
      f0eb46fc
  21. 29 May, 2019 1 commit
  22. 23 May, 2019 1 commit
  23. 22 May, 2019 1 commit
  24. 14 May, 2019 1 commit
  25. 30 Apr, 2019 3 commits
  26. 01 Apr, 2019 1 commit
  27. 21 Mar, 2019 1 commit
  28. 13 Mar, 2019 1 commit
  29. 30 Jan, 2019 1 commit
  30. 29 Jan, 2019 1 commit
  31. 16 Jan, 2019 1 commit
  32. 04 Jan, 2019 1 commit
  33. 19 Dec, 2018 1 commit
    • Sebastian Kaspari's avatar
      Refactor EngineSessionHolder to keep a reference to an EngineSession or EngineSessionState. · 92a12fbc
      Sebastian Kaspari authored
      The main change here is that EngineSessionHolder can now hold an EngineState and this state
      is used when we need to create an EngineSession (which will clear the state). This has the
      following advantages:
      
      * When restoring we can just attach the EngineState and do not need to create the
        EngineSession immediately. With that we do not load all the EngineSessions and everything
        at once. Initially only the selected EngineSession will be created and loaded. That will
        make the restore faster and use less resources when restoring a lot of sessions.
      
      * (Not in this commit, for a follow-up) It allows us to close EngineSession instances and
        just keep the EngineState around until we need the EngineSession again. That's something
        we could do in low memory situations or when there are just too many sessions/tabs open
        to be performant (e.g. only keep the last recently used EngineSession instances around).
      92a12fbc
  34. 18 Dec, 2018 1 commit
  35. 30 Nov, 2018 1 commit
  36. 28 Nov, 2018 1 commit