1. 15 Jan, 2021 2 commits
    • Kathleen Brade's avatar
      Bug 4234: Use the Firefox Update Process for Tor Browser. · 9e8c0b0b
      Kathleen Brade authored and Matthew Finkel's avatar Matthew Finkel committed
      The following files are never updated:
        TorBrowser/Data/Browser/profiles.ini
        TorBrowser/Data/Browser/profile.default/bookmarks.html
        TorBrowser/Data/Tor/torrc
      Mac OS: Store update metadata under TorBrowser/UpdateInfo.
      Removed the %OS_VERSION% component from the update URL (13047) and
        added support for minSupportedOSVersion, an attribute of the
        <update> element that may be used to trigger Firefox's
        "unsupported platform" behavior.
      Hide the "What's new" links (set app.releaseNotesURL value to about:blank).
      Windows: disable "runas" code path in updater (15201).
      Windows: avoid writing to the registry (16236).
      Also includes fixes for tickets 13047, 13301, 13356, 13594, 15406,
        16014, 16909, 24476, and 25909.
      
      Also fix Bug 26049: reduce the delay before the update prompt is displayed.
      Instead of Firefox's 2 days, we use 1 hour (after which time the update
      doorhanger will be displayed).
      
      Also fix bug 27221: purge the startup cache if the Tor Browser
      version changed (even if the Firefox version and build ID did
      not change), e.g., after a minor Tor Browser update.
      
      Also fix 32616: Disable GetSecureOutputDirectoryPath() functionality.
      
      Bug 26048: potentially confusing "restart to update" message
      
      Within the update doorhanger, remove the misleading message that mentions
      that windows will be restored after an update is applied, and replace the
      "Restart and Restore" button label with an existing
      "Restart to update Tor Browser" string.
      
      Bug 28885: notify users that update is downloading
      
      Add a "Downloading Tor Browser update" item which appears in the
      hamburger (app) menu while the update service is downloading a MAR
      file. Before this change, the browser did not indicate to the user
      that an update was in progress, which is especially confusing in
      Tor Browser because downloads often take some time. If the user
      clicks on the new menu item, the about dialog is opened to allow
      the user to see download progress.
      
      As part of this fix, the update service was changed to always show
      update-related messages in the hamburger menu, even if the update
      was started in the foreground via the about dialog or via the
      "Check for Tor Browser Update" toolbar menu item. This change is
      consistent with the Tor Browser goal of making sure users are
      informed about the update process.
      
      Removed #28885 parts of this patch which have been uplifted to Firefox.
      9e8c0b0b
    • Kathleen Brade's avatar
      Bug 19121: reinstate the update.xml hash check · 583fa055
      Kathleen Brade authored and Matthew Finkel's avatar Matthew Finkel committed
      Revert most changes from Mozilla Bug 1373267 "Remove hashFunction and
      hashValue attributes from nsIUpdatePatch and code related to these
      attributes." Changes to the tests were not reverted; the tests have
      been changed significantly and we do not run automated updater tests
      for Tor Browser at this time.
      
      Also partial revert of commit f1241db6.
      
      Revert the nsUpdateService.js changes from Mozilla Bug 862173 "don't
      verify mar file hash when using mar signing to verify the mar file
      (lessens main thread I/O)."
      
      Changes to the tests were not reverted; the tests have been changed
      significantly and we do not run automated updater tests for
      Tor Browser at this time.
      
      We kept the addition to the AppConstants API in case other JS code
      references it in the future.
      583fa055
  2. 10 Dec, 2020 1 commit
  3. 07 Dec, 2020 1 commit
  4. 03 Dec, 2020 2 commits
  5. 06 Oct, 2020 1 commit
    • Kirk Steuber's avatar
      Bug 1668096 - Replace activeUpdate with downloadingUpdate and readyUpdate... · 839b14ef
      Kirk Steuber authored
      Bug 1668096 - Replace activeUpdate with downloadingUpdate and readyUpdate r=mhowell,preferences-reviewers
      
      This patch does not make the necessary replacement in tests. Those changes will be made in a later patch in this stack.
      
      Some additional, related changes are also made in this patch:
      cleanupActiveUpdate is being replaced with cleanupDownloadingUpdate and cleanupReadyUpdate. The two new functions currently do very similar things, but separating them will allow us to have each function clean up the right update, once we fully support more than one update per session.
      The old mechanism to add something to the update history was for it to be assigned to activeUpdate, and then to assign null to activeUpdate. We now need to assign active updates to be null without adding them to the history. As an example, we need to set downloadingUpdate to null when the download completes, but it shouldn't be added to the history at that point. To address this, an explicit addUpdateToHistory function has been added, and assigning null to either active update variable no longer moves the update to the update history.
      
      Differential Revision: https://phabricator.services.mozilla.com/D92289
      839b14ef
  6. 29 Sep, 2020 1 commit
  7. 03 Dec, 2020 1 commit
  8. 30 Nov, 2020 2 commits
  9. 23 Sep, 2020 1 commit
  10. 07 Aug, 2020 1 commit
  11. 06 Aug, 2020 1 commit
  12. 20 Oct, 2020 2 commits
  13. 19 Oct, 2020 1 commit
  14. 03 Aug, 2020 1 commit
  15. 23 Jun, 2020 1 commit
  16. 22 Jun, 2020 1 commit
  17. 17 Jun, 2020 1 commit
  18. 10 Jul, 2020 1 commit
  19. 05 May, 2020 1 commit
    • Ian Moody's avatar
      Bug 1536556 - Replace raw thrown Cr.ERRORs with Components.Exception.... · 011b59d5
      Ian Moody authored
      Bug 1536556 - Replace raw thrown Cr.ERRORs with Components.Exception. r=mossop,remote-protocol-reviewers,marionette-reviewers,whimboo,necko-reviewers,geckoview-reviewers,valentin,agi
      
      Raw Cr.ERROR don't get stack information, same as throwing JS literals instead
      of `new Error()`s.
      
      This was done automatically with a new eslint rule that will be introduced in
      the next commit.  One instance of a raw Cr.ERROR was not replaced since it is
      used in a test that specifically checks the preservation of raw Cr values in
      XPCJS.  The rule will be disabled for that instance.
      
      Differential Revision: https://phabricator.services.mozilla.com/D28073
      011b59d5
  20. 29 Mar, 2020 1 commit
  21. 27 Mar, 2020 4 commits
  22. 24 Mar, 2020 2 commits
  23. 27 Feb, 2020 3 commits
    • Kirk Steuber's avatar
      Bug 1615087 - Remove expiring BITS update telemetry, supporting code, and... · d06097f7
      Kirk Steuber authored
      Bug 1615087 - Remove expiring BITS update telemetry, supporting code, and tests specific to it r=mhowell
      
      This patch is effectively very close to backing out Bug 1539154, which added telemetry to monitor download times of BITS vs our internal downloader. This was useful to make sure we weren't worsening update times when we added BITS support. But at this point, these probes have outlived their usefulness to us.
      
      Also adds the TelemetryTestUtils import to browser/components/urlbar/tests/browser/interventions_update/head.js since it was relying on that being imported in toolkit/mozapps/update/tests/data/shared.js where it is no longer needed.
      
      Differential Revision: https://phabricator.services.mozilla.com/D64477
      
      --HG--
      extra : moz-landing-system : lando
      d06097f7
    • Daniel Varga's avatar
      Backed out changeset 78d142f0f2f6 (bug 1615087) for linting failure at... · 88355d1b
      Daniel Varga authored
      Backed out changeset 78d142f0f2f6 (bug 1615087) for linting failure at /builds/worker/checkouts/gecko/browser/components/urlbar/tests/browser/interventions_update/head.j
      
      CLOSED TREE
      88355d1b
    • Kirk Steuber's avatar
      Bug 1615087 - Remove expiring BITS update telemetry, supporting code, and... · 79e21c00
      Kirk Steuber authored
      Bug 1615087 - Remove expiring BITS update telemetry, supporting code, and tests specific to it r=mhowell
      
      This patch is effectively very close to backing out Bug 1539154, which added telemetry to monitor download times of BITS vs our internal downloader. This was useful to make sure we weren't worsening update times when we added BITS support. But at this point, these probes have outlived their usefulness to us.
      
      Differential Revision: https://phabricator.services.mozilla.com/D64477
      
      --HG--
      extra : moz-landing-system : lando
      79e21c00
  24. 04 Feb, 2020 1 commit
  25. 12 Dec, 2019 1 commit
    • Emma Malysz's avatar
      Bug 1601090, rename .xul files to .xhtml in toolkit/mozapps r=mossop · be023856
      Emma Malysz authored
      Differential Revision: https://phabricator.services.mozilla.com/D55837
      
      --HG--
      rename : toolkit/mozapps/downloads/content/unknownContentType.xul => toolkit/mozapps/downloads/content/unknownContentType.xhtml
      rename : toolkit/mozapps/extensions/content/blocklist.xul => toolkit/mozapps/extensions/content/blocklist.xhtml
      rename : toolkit/mozapps/extensions/content/extensions.xul => toolkit/mozapps/extensions/content/extensions.xhtml
      rename : toolkit/mozapps/handling/content/dialog.xul => toolkit/mozapps/handling/content/dialog.xhtml
      rename : toolkit/mozapps/update/content/updateElevation.xul => toolkit/mozapps/update/content/updateElevation.xhtml
      extra : moz-landing-system : lando
      be023856
  26. 29 Oct, 2019 1 commit
  27. 21 Oct, 2019 2 commits
  28. 20 Sep, 2019 1 commit
  29. 14 Sep, 2019 1 commit