1. 01 Jul, 2021 1 commit
  2. 30 Jun, 2021 1 commit
  3. 23 Jun, 2021 1 commit
  4. 02 Jun, 2021 12 commits
    • Richard Pospesel's avatar
      Bug 27476: Implement about:torconnect captive portal within Tor Browser · 5fecbec5
      Richard Pospesel authored and Matthew Finkel's avatar Matthew Finkel committed
      - implements new about:torconnect page as tor-launcher replacement
      - adds tor connection status to url bar and tweaks UX when not online
      - adds new torconnect component to browser
      - tor process management functionality remains implemented in tor-launcher through the TorProtocolService module
      - the onion pattern from about:tor migrated to an .inc.xhtml file now used by both about:tor and about:torconnect
      - various design tweaks and resusability fixes to onion pattern
      - adds warning/error box to about:preferences#tor when not connected to tor
      - explicitly allows about:torconnect URIs to ignore Resist Fingerprinting (RFP)
      - various tweaks to info-pages.inc.css for about:torconnect (also affects other firefox info pages)
      5fecbec5
    • sanketh's avatar
      40209: Implement Basic Crypto Safety · 363e84c8
      sanketh authored and Matthew Finkel's avatar Matthew Finkel committed
      Adds a CryptoSafety actor which detects when you've copied a crypto
      address from a HTTP webpage and shows a warning.
      
      Closes #40209.
      
      Bug 40428: Fix string attribute names
      363e84c8
    • Alex Catarineu's avatar
      f57ab6bd
    • Alex Catarineu's avatar
      Bug 40091: Load HTTPS Everywhere as a builtin addon in desktop · 525ccaee
      Alex Catarineu authored and Matthew Finkel's avatar Matthew Finkel committed
      This loads HTTPS Everywhere as a builtin addon from a hardcoded
      resource:// URI in desktop. It also ensures that the non-builtin
      HTTPS Everywhere addon is always uninstalled on browser startup.
      
      The reason of making this desktop-only is that there are some issues
      when installing a builtin extension from geckoview side, making
      the extension not available on first startup. So, at least for
      now we handle the Fenix case separately. See #40118 for a followup
      for investigating these.
      525ccaee
    • Alex Catarineu's avatar
      Bug 40073: Disable remote Public Suffix List fetching · ea452749
      Alex Catarineu authored and Matthew Finkel's avatar Matthew Finkel committed
      In https://bugzilla.mozilla.org/show_bug.cgi?id=1563246 Firefox implemented
      fetching the Public Suffix List via RemoteSettings and replacing the default
      one at runtime, which we do not want.
      ea452749
    • Alex Catarineu's avatar
      Bug 21952: Implement Onion-Location · 73c48121
      Alex Catarineu authored and Matthew Finkel's avatar Matthew Finkel committed
      Whenever a valid Onion-Location HTTP header (or corresponding HTML
      <meta> http-equiv attribute) is found in a document load, we either
      redirect to it (if the user opted-in via preference) or notify the
      presence of an onionsite alternative with a badge in the urlbar.
      73c48121
    • Alex Catarineu's avatar
      Bug 28005: Implement .onion alias urlbar rewrites · d0764114
      Alex Catarineu authored and Matthew Finkel's avatar Matthew Finkel committed
      A custom HTTPS Everywhere update channel is installed,
      which provides rules for locally redirecting some memorable
      .tor.onion URLs to non-memorable .onion URLs.
      
      When these redirects occur, we also rewrite the URL in the urlbar
      to display the human-memorable hostname instead of the actual
      .onion.
      
      Bug 34196: Update site info URL with the onion name
      d0764114
    • Alex Catarineu's avatar
      Bring back old Firefox onboarding · ba19fef0
      Alex Catarineu authored and Matthew Finkel's avatar Matthew Finkel committed
      Revert "Bug 1462415 - Delete onboarding system add-on r=Standard8,k88hudson"
      
      This reverts commit f7ffd78b.
      
      Revert "Bug 1498378 - Actually remove the old onboarding add-on's prefs r=Gijs"
      
      This reverts commit 057fe36f.
      
      Bug 28822: Convert onboarding to webextension
      
      Partially revert 1564367 (controlCenter in UITour.jsm)
      ba19fef0
    • Alex Catarineu's avatar
      Bug 31575: Replace Firefox Home (newtab) with about:tor · 461b5da7
      Alex Catarineu authored and Matthew Finkel's avatar Matthew Finkel committed
      Avoid loading AboutNewTab in BrowserGlue.jsm in order
      to avoid several network requests that we do not need. Besides,
      about:newtab will now point to about:blank or about:tor (depending
      on browser.newtabpage.enabled) and about:home will point to
      about:tor.
      461b5da7
    • Kathleen Brade's avatar
      Bug 21431: Clean-up system extensions shipped in Firefox · 761744a9
      Kathleen Brade authored and Matthew Finkel's avatar Matthew Finkel committed
      Only ship the pdfjs extension.
      761744a9
    • Kathleen Brade's avatar
      Bug 16940: After update, load local change notes. · 35c087c5
      Kathleen Brade authored and Matthew Finkel's avatar Matthew Finkel committed
      Add an about:tbupdate page that displays the first section from
      TorBrowser/Docs/ChangeLog.txt and includes a link to the remote
      post-update page (typically our blog entry for the release).
      
      Always load about:tbupdate in a content process, but implement the
      code that reads the file system (changelog) in the chrome process
      for compatibility with future sandboxing efforts.
      
      Also fix bug 29440. Now about:tbupdate is styled as a fairly simple
      changelog page that is designed to be displayed via a link that is on
      about:tor.
      35c087c5
    • 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
  5. 04 Jun, 2020 1 commit
  6. 01 Jun, 2020 1 commit
  7. 29 May, 2020 1 commit
  8. 06 May, 2020 1 commit
  9. 29 May, 2020 1 commit
  10. 20 May, 2020 1 commit
  11. 19 May, 2020 1 commit
  12. 18 May, 2020 1 commit
  13. 15 May, 2020 3 commits
  14. 14 May, 2020 3 commits
  15. 13 May, 2020 2 commits
  16. 12 May, 2020 2 commits
  17. 06 May, 2020 3 commits
    • Liang-Heng Chen's avatar
    • Gijs Kruitbosch's avatar
      Bug 1633790 - allow PDF.js use when we've misled the user into misconfiguring... · 6c3c9b5b
      Gijs Kruitbosch authored
      Bug 1633790 - allow PDF.js use when we've misled the user into misconfiguring PDF handlers, r=jaws,mattwoodrow
      
      Prior to this patch, PDF.js tracks both its own 'disabled' pref (which is used
      by enterprise policy) and whether it is the default handler per the handler
      service - but it tracks both in one bool, which determines whether its
      streamconverter registers.
      
      Really, what we want is to never use PDF.js if it's preffed off.
      
      However, if there is some other default, it should be acceptable to use PDF.js
      in some circumstances, like for <embed> or <object>s where otherwise we
      would show no content at all.
      
      Even for toplevel PDFs, if the user has configured Firefox to open PDFs in
      an external helper app which is Firefox (which is currently an easy mistake
      to make in the unknownContentType dialog), or has it set to the OS default,
      but has changed their OS default to Firefox, we really still want to open
      those PDFs with PDF.js.
      
      This patch fixes all of this by splitting out the pref tracking from the
      handler state tracking. Only the pref will completely disable PDF.js.
      
      Then, in the streamconverter code, we check whether PDF.js should be used for
      PDFs, and if there's a misconfiguration that we can correct. This code is
      invoked from the parent process when we load PDFs in frames or toplevel
      documents, and will prevent us from invoking PDF.js in the child if the user
      would prefer that not to happen.
      
      As a driveby, this cleans up how we track the pref inside PDF.js, and how we
      get notified of changes to the handler - we were missing changes made in the
      unknown content type dialog, so it seemed worth making it generic.
      
      Differential Revision: https://phabricator.services.mozilla.com/D73510
      6c3c9b5b
    • Gijs Kruitbosch's avatar
      Bug 1633365 - stop loading page style actors except in tabbrowser browsers, r=florian · b63c2a54
      Gijs Kruitbosch authored
      I filed a bug for the generic version of this as bug 1635131, but we can
      stop the immediate problem here by just not running this actor except
      for tabbrowser browsing contexts.
      
      Differential Revision: https://phabricator.services.mozilla.com/D73715
      b63c2a54
  18. 05 May, 2020 2 commits
  19. 01 May, 2020 1 commit
  20. 29 Apr, 2020 1 commit