1. 01 Jul, 2021 1 commit
  2. 30 Jun, 2021 1 commit
  3. 02 Jun, 2021 5 commits
    • Kathleen Brade's avatar
      Bug 32418: Allow updates to be disabled via an enterprise policy. · 96144981
      Kathleen Brade authored and Matthew Finkel's avatar Matthew Finkel committed
      Restrict the Enterprise Policies mechanism to only consult a
      policies.json file (avoiding the Windows Registry and macOS's
      file system attributes).
      
      Add a few disabledByPolicy() checks to the update service to
      avoid extraneous (and potentially confusing) log messages when
      updates are disabled by policy.
      
      Sample content for distribution/policies.json:
      {
        "policies": {
          "DisableAppUpdate": true
        }
      }
      
      On Linux, avoid reading policies from /etc/firefox/policies/policies.json
      96144981
    • Kathleen Brade's avatar
      Bug 4234: Use the Firefox Update Process for Tor Browser. · df0d0d0f
      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 Br...
      df0d0d0f
    • Kathleen Brade's avatar
      Bug 19121: reinstate the update.xml hash check · ab25639f
      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.
      ab25639f
    • Mark Smith's avatar
      Bug 1642754 - Update prompts should not depend on how update was initiated r=bytesized · 5c879844
      Mark Smith authored and Matthew Finkel's avatar Matthew Finkel committed
      Show update badge and doorhanger when entering the "pending"
      state for foreground updates.
      
      Differential Revision: https://phabricator.services.mozilla.com/D79903
      5c879844
    • Mark Smith's avatar
      Bug 1642404 - add an option to show that an update is being downloaded... · 1dbe18de
      Mark Smith authored and Matthew Finkel's avatar Matthew Finkel committed
      Bug 1642404 - add an option to show that an update is being downloaded r=bytesized,fluent-reviewers,flod
      
      Add support for a hidden preference named app.update.notifyDuringDownload
      that, when set to true, causes a "Downloading update" message to appear
      in the app menu during a MAR download. Clicking the message opens the
      about box so the user can see detailed progress information.
      
      Differential Revision: https://phabricator.services.mozilla.com/D77688
      1dbe18de
  4. 10 Dec, 2020 1 commit
  5. 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
  6. 29 Mar, 2020 1 commit
  7. 27 Mar, 2020 4 commits
  8. 24 Mar, 2020 2 commits
  9. 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
  10. 04 Feb, 2020 1 commit
  11. 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
  12. 29 Oct, 2019 1 commit
  13. 21 Oct, 2019 2 commits
  14. 20 Sep, 2019 1 commit
  15. 14 Sep, 2019 1 commit
  16. 01 Aug, 2019 2 commits
  17. 31 Jul, 2019 1 commit
    • Robert Strong's avatar
      Bug 1567077 - don't try to update when the update.status file is read only. r=bytesized · 613550c9
      Robert Strong authored
      When checking for an update during startup, open the update.status file with read and write access so repeated update attempts are prevented when there is only read access to the update.status file.
      When loading the active-update.xml file after startup, open it with both read and write access so the active-update.xml isn't loaded when there is only read access and the client will still receive manual update notifications.
      On Windows, when opening the active-update.xml file with both read and write access fails attempt to fix the update directory permissions.
      When checking if it is possible to apply updates, first check for write access to the update directory so OS X no longer always returns true and Windows no longer always returns true when the maintenance service can be used.
      Sets security.turn_off_all_security_so_that_viruses_can_take_over_this_computer to true in the app update xpcshell tests so Cu.isInAutomation is true when running the tests.
      
      Differential Revision: https://phabricator.services.mozilla.com/D39601
      
      --HG--
      rename : toolkit/mozapps/update/tests/unit_base_updater/marAppApplyUpdateSuccess.js => toolkit/mozapps/update/tests/unit_base_updater/marAppApplyUpdateSkippedWriteAccess_win.js
      extra : moz-landing-system : lando
      613550c9
  18. 09 Jul, 2019 1 commit
  19. 25 Jun, 2019 1 commit
  20. 05 Jul, 2019 1 commit
  21. 27 Jun, 2019 1 commit
  22. 25 Jun, 2019 1 commit
  23. 11 Jun, 2019 1 commit
  24. 08 Jun, 2019 1 commit
  25. 06 Jun, 2019 2 commits
  26. 22 May, 2019 1 commit
    • Robert Strong's avatar
      Bug 1552853 - Fix the update UI so it displays restart when it should when... · fc1f4c97
      Robert Strong authored
      Bug 1552853 - Fix the update UI so it displays restart when it should when update staging fails. r=mhowell
      
      Fixes the case reported where disabling the maintenance service caused the UI to display Applying due to the update staging failure.
      Added new error codes for the two cases where pending was written to the update.status file when staging failed.
      Added code to UpdateService.jsm to set the update.status to pending when either of the two new error codes are in the update.status file.
      Added two new tests that verify the UI and simulate the failure condition in updater.cpp.
      
      Differential Revision: https://phabricator.services.mozilla.com/D32177
      
      --HG--
      extra : moz-landing-system : lando
      fc1f4c97
  27. 02 May, 2019 1 commit