Skip to content
Snippets Groups Projects
  1. Oct 21, 2024
    • Kathleen Brade's avatar
      Bug 4234: Use the Firefox Update Process for Base Browser. · 1bf01d0d
      Kathleen Brade authored and Pier Angelo Vendrame's avatar Pier Angelo Vendrame committed
      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 27221: purge the startup cache if the Base Browser
      version changed (even if the Firefox version and build ID did
      not change), e.g., after a minor Base 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 Base 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.
      1bf01d0d
  2. Sep 05, 2024
  3. Jul 15, 2024
  4. May 01, 2024
  5. Feb 05, 2024
  6. Sep 01, 2023
  7. Aug 30, 2023
  8. Jul 26, 2023
  9. Jul 08, 2023
  10. Jun 20, 2023
  11. Jun 05, 2023
  12. Jun 02, 2023
  13. May 31, 2023
  14. May 30, 2023
  15. May 29, 2023
  16. May 25, 2023
  17. May 24, 2023
  18. May 23, 2023
    • Eemeli Aro's avatar
      Bug 1793557 - Convert Extension.jsm strings to Fluent.... · 411a5290
      Eemeli Aro authored
      Bug 1793557 - Convert Extension.jsm strings to Fluent. r=mkmelin,geckoview-reviewers,robwu,flod,owlish
      
      This changes the arguments of `ExtensionData.formatPermissionStrings()`.
      The second `bundle` arg is dropped, and a `localization` option is added.
      Call sites in m-c are updated, but this will also need a matching update for Thunderbird.
      A few Thunderbird test cases will also need to be updated,
      as they currently point to a non-existing localization file paths
      "messenger/addons.ftl" and "messenger/addonPermissions.ftl".
      
      As discussed at the addon workweek,
      the Fluent l10n keys for extension permissions match the pattern:
      
          webext-perms-description-{name}
      
      where `{name}` is the permission's sanitized name.
      A fluent-lint exception is added for the capitalization of these generated names.
      To allow for message updates and subsequent l10n identifier updates,
      a `PERMISSION_L10N_ID_OVERRIDES` map is provided.
      
      Because Fluent localization keys are not enumerable
      and attempting to format a missing key is an error,
      the `PERMISSIONS_WITH_MESSAGE` set must be kept in sync with message updates.
      
      Differential Revision: https://phabricator.services.mozilla.com/D158663
      411a5290
    • Gijs Kruitbosch's avatar
      Bug 1834499 - fix path globbing for extensions in stylelint linter and fix... · a8576ab0
      Gijs Kruitbosch authored
      Bug 1834499 - fix path globbing for extensions in stylelint linter and fix debugger styles that this starts noticing, r=Standard8,devtools-reviewers
      
      For some reason I didn't fully apply the suggestion in
      https://phabricator.services.mozilla.com/D177477#inline-983366
      and this is affecting some invocations of stylelint (but not others, for
      reasons I don't fully understand). This commit both fixes this oversight and
      fixes up some debugger styles that get flagged now that they're linted
      appropriately.
      
      Differential Revision: https://phabricator.services.mozilla.com/D178531
      a8576ab0
  19. May 22, 2023
  20. May 21, 2023
  21. May 20, 2023
  22. May 18, 2023
  23. May 17, 2023
Loading