Skip to content
Snippets Groups Projects
  1. Sep 05, 2023
  2. Sep 20, 2023
  3. Jul 26, 2023
  4. Aug 01, 2023
  5. Jun 19, 2023
  6. Jun 05, 2023
  7. Jun 02, 2023
  8. May 31, 2023
  9. May 30, 2023
    • mcheang's avatar
      Bug 1648188 - Fix SearchService init failures so that the address bar can be... · 50ce5c5c
      mcheang authored
      Bug 1648188 - Fix SearchService init failures so that the address bar can be used to search history and bookmarks. r=Standard8,mak
      
      This patch refactors the SearchService private initialized variables and how
      the SearchService stores its initialization status. These changes capture whether
      the SearchService has succeeded, failed or hasn't finished initialization yet.
      
      There are also changes made to UrlbarSearchUtils on handling when SearchService
      has failed to initialize or when it hasn't finished initializing yet and we wait.
      In the case where the SearchService has failed on initialization, We allow
      the code to continue so that it can reach UrlbarProviderPlaces. Once we
      are able to reach UrlbarProviderPlaces, we can make database calls for the user's
      history and bookmarks. This allows the user to interact with the addressbar and
      search their history and bookmarks even if SearchService has failed to initialize.
      
      Differential Revision: https://phabricator.services.mozilla.com/D176936
      50ce5c5c
  10. May 27, 2023
  11. May 24, 2023
  12. May 23, 2023
  13. May 24, 2023
  14. May 23, 2023
  15. May 20, 2023
  16. May 17, 2023
  17. May 24, 2023
  18. May 15, 2023
  19. May 09, 2023
  20. May 04, 2023
    • valenting's avatar
      Bug 1828643 - Make sure LOAD_TRR_DISABLED_MODE gets passed through... · d245bc86
      valenting authored
      Bug 1828643 - Make sure LOAD_TRR_DISABLED_MODE gets passed through defaultLoadFlags when browsing context is replaced r=necko-reviewers,kershaw
      
      When the user clicks continue this time in the DoH fallback warning page
      we want to set the defaultLoadFlags to LOAD_TRR_DISABLED_MODE so all of
      the pages & subresources in the tab will not use TRR from that point
      forward.
      
      Setting it directly on docshell.defaultLoadFlags seems to not have the correct
      behaviour when the page is using the Cross-Origin-Opener-Policy header,
      as that causes the DocumentChannel to do a cross process redirect and
      recreate the browsing context.
      
      Setting the defaultLoadFlags on the browsingContext directly and
      adding the field to `CanonicalBrowsingContext::ReplacedBy` seems to lead to
      the expected behaviour.
      
      Differential Revision: https://phabricator.services.mozilla.com/D176959
      d245bc86
  21. May 03, 2023
  22. May 02, 2023
  23. May 01, 2023
  24. Apr 20, 2023
  25. Apr 22, 2023
  26. Apr 18, 2023
  27. Apr 14, 2023
Loading