Skip to content
Snippets Groups Projects
  1. May 24, 2023
  2. May 23, 2023
  3. May 20, 2023
  4. Mar 02, 2023
  5. Dec 13, 2022
  6. Dec 01, 2022
    • Nika Layzell's avatar
      Bug 1793463 - Part 6: Remove nsIProtocolHandler.{defaultPort,protocolFlags},... · 1f06e7ba
      Nika Layzell authored
      Bug 1793463 - Part 6: Remove nsIProtocolHandler.{defaultPort,protocolFlags}, r=necko-reviewers,valentin
      
      This removes all implementations of these types. Some implementations in JS
      code were also removed in the previous part, when updating tests to use
      `Services.io.registerProtocolHandler`.
      
      Code which used to access these members should go through the IOService now
      instead.
      
      Differential Revision: https://phabricator.services.mozilla.com/D162805
      1f06e7ba
    • Nika Layzell's avatar
      Bug 1793463 - Part 5: Stop using contractids to fetch protocol handlers,... · 98304d12
      Nika Layzell authored
      Bug 1793463 - Part 5: Stop using contractids to fetch protocol handlers, r=necko-reviewers,xpcom-reviewers,webdriver-reviewers,whimboo,valentin,kmag
      
      This patch replaces the previous ContractID-based lookup system for protocol
      handlers, and replaces it with a new custom system in nsIOService. It will be
      pre-populated with non-overridable static protocol handlers using the
      StaticComponents infrastructure added in the previous part, and callers can
      also dynamically register new protocol handlers at runtime.
      
      This new system is intended to provide access to the default port and
      non-dynamic protocol flags off-main-thread, by requiring these values to be
      provided up-front as constants, rather than getting them from the xpcom
      interface. The data is then guarded by an RWLock.
      
      Callers which look up specific handlers by their contractID are not changed, as
      the contract IDs for existing handlers have not been changed, so the lookup
      will still succeed.
      
      This change as-implemented breaks the nsGIOProtocolHandler on Linux, as it
      removes the special code which would try to use that handler for some
      protocols. This will be fixed in a later part by making the
      nsGIOProtocolHandler use the dynamic registration APIs to register and
      un-register protocol handlers at runtime in response to the GIO pref.
      
      Differential Revision: https://phabricator.services.mozilla.com/D162804
      98304d12
    • Marian-Vasile Laza's avatar
      Backed out 7 changesets (bug 1793463) for causing bustages on nsIOService.cpp. CLOSED TREE · 74920251
      Marian-Vasile Laza authored
      Backed out changeset 47c3acb30de2 (bug 1793463)
      Backed out changeset 71afe900eb17 (bug 1793463)
      Backed out changeset d168599a269e (bug 1793463)
      Backed out changeset d0f18d300818 (bug 1793463)
      Backed out changeset a116e6f089f2 (bug 1793463)
      Backed out changeset eba1123c8b56 (bug 1793463)
      Backed out changeset 68a3eb8a3057 (bug 1793463)
      74920251
  7. Nov 30, 2022
    • Nika Layzell's avatar
      Bug 1793463 - Part 6: Remove nsIProtocolHandler.{defaultPort,protocolFlags},... · 20db36ce
      Nika Layzell authored
      Bug 1793463 - Part 6: Remove nsIProtocolHandler.{defaultPort,protocolFlags}, r=necko-reviewers,valentin
      
      This removes all implementations of these types. Some implementations in JS
      code were also removed in the previous part, when updating tests to use
      `Services.io.registerProtocolHandler`.
      
      Code which used to access these members should go through the IOService now
      instead.
      
      Differential Revision: https://phabricator.services.mozilla.com/D162805
      20db36ce
    • Nika Layzell's avatar
      Bug 1793463 - Part 5: Stop using contractids to fetch protocol handlers,... · 9cc8ee8c
      Nika Layzell authored
      Bug 1793463 - Part 5: Stop using contractids to fetch protocol handlers, r=necko-reviewers,xpcom-reviewers,webdriver-reviewers,whimboo,valentin,kmag
      
      This patch replaces the previous ContractID-based lookup system for protocol
      handlers, and replaces it with a new custom system in nsIOService. It will be
      pre-populated with non-overridable static protocol handlers using the
      StaticComponents infrastructure added in the previous part, and callers can
      also dynamically register new protocol handlers at runtime.
      
      This new system is intended to provide access to the default port and
      non-dynamic protocol flags off-main-thread, by requiring these values to be
      provided up-front as constants, rather than getting them from the xpcom
      interface. The data is then guarded by an RWLock.
      
      Callers which look up specific handlers by their contractID are not changed, as
      the contract IDs for existing handlers have not been changed, so the lookup
      will still succeed.
      
      This change as-implemented breaks the nsGIOProtocolHandler on Linux, as it
      removes the special code which would try to use that handler for some
      protocols. This will be fixed in a later part by making the
      nsGIOProtocolHandler use the dynamic registration APIs to register and
      un-register protocol handlers at runtime in response to the GIO pref.
      
      Differential Revision: https://phabricator.services.mozilla.com/D162804
      9cc8ee8c
  8. Nov 17, 2022
  9. Oct 24, 2022
  10. Oct 19, 2022
  11. Oct 17, 2022
  12. Sep 28, 2022
  13. Sep 20, 2022
  14. Sep 12, 2022
  15. Jul 25, 2022
  16. Jul 11, 2022
  17. May 17, 2022
    • Andrew McCreight's avatar
      Bug 1514936, part 1 - Remove the outer argument to nsIFactory::createInstance.... · c8c5c819
      Andrew McCreight authored
      Bug 1514936, part 1 - Remove the outer argument to nsIFactory::createInstance. r=xpcom-reviewers,preferences-reviewers,nika,Gijs
      
      This patch won't actually build, because a few bits of code are used
      for both nsIFactory::createInstance and static components, and static
      components are not fixed until the next patch.
      
      The first place is nsLoadGroupConstructor, which uses an nsIFactory
      macro to create a static component constructor. (This could be worked
      around by expanding the macro to the state before this patch.)
      
      The other issue is that nsAppShellConstructor is used in an nsIFactory
      on OSX, but as a static component on all other platforms. This could
      be worked around by wrapping nsAppShellConstructor in an adaptor that
      passes in the extra null argument to nsAppShellConstructor.
      
      Differential Revision: https://phabricator.services.mozilla.com/D146456
      c8c5c819
  18. Apr 05, 2022
  19. Mar 11, 2022
  20. Mar 10, 2022
  21. Mar 04, 2022
  22. Dec 23, 2021
  23. Dec 22, 2021
  24. Oct 11, 2021
  25. Sep 06, 2021
  26. Aug 25, 2021
    • Andi-Bogdan Postelnicu's avatar
      Bug 1725145 - Preparation for the hybrid build env.... · 2fc4f70e
      Andi-Bogdan Postelnicu authored
      Bug 1725145 - Preparation for the hybrid build env. r=necko-reviewers,firefox-build-system-reviewers,valentin,glandium
      
      Automatically generated path that adds flag `REQUIRES_UNIFIED_BUILD = True` to `moz.build`
      when the module governed by the build config file is not buildable outside on the unified environment.
      
      This needs to be done in order to have a hybrid build system that adds the possibility of combing
      unified build components with ones that are built outside of the unified eco system.
      
      Differential Revision: https://phabricator.services.mozilla.com/D122345
      2fc4f70e
  27. Aug 12, 2021
Loading