1. 21 Feb, 2018 1 commit
  2. 02 Feb, 2018 1 commit
  3. 25 Jan, 2018 1 commit
  4. 23 Jan, 2018 1 commit
  5. 18 Jan, 2018 1 commit
  6. 10 Jan, 2018 2 commits
  7. 21 Dec, 2017 1 commit
  8. 18 Dec, 2017 3 commits
  9. 17 Dec, 2017 1 commit
  10. 09 Nov, 2017 2 commits
  11. 08 Nov, 2017 1 commit
  12. 27 Oct, 2017 1 commit
  13. 23 Oct, 2017 3 commits
  14. 18 Oct, 2017 1 commit
  15. 17 Oct, 2017 1 commit
  16. 24 Oct, 2017 1 commit
  17. 22 Sep, 2017 2 commits
  18. 21 Sep, 2017 1 commit
  19. 15 Sep, 2017 1 commit
  20. 30 Aug, 2017 1 commit
  21. 29 Aug, 2017 1 commit
  22. 23 Aug, 2017 2 commits
    • Arthur Edelstein's avatar
      Bug 20375: Warn users after entering fullscreen mode. · f6b52b8d
      Arthur Edelstein authored and Georg Koppen's avatar Georg Koppen committed
      When the browser window is maximized, we show users a notification
      warning that maximizing the screen is fingerprintable. We should
      show this warning when the window enters fullscreen mode as well.
      This change is especially important for macOS, which uses
      window.STATE_FULLSCREEN instead of window.STATE_MAXIMIZED when
      the user clicks the "maximize" button on the window title bar.
      f6b52b8d
    • Arthur Edelstein's avatar
      Bug 22989: Fix dimensions of new windows on macOS. · 97380447
      Arthur Edelstein authored and Georg Koppen's avatar Georg Koppen committed
      Before this patch, a new Tor Browser window, non-maximized,
      was showing a "don't maximize this window" notification briefly
      as soon as it was first displayed. Worse, the notification box
      that appears causes the window height to increase by 10 or 11
      pixels and thus breaks our desired window dimension rounding.
      
      Our intended behavior is that this notification only be shown
      when the window is maximized by the user. I discovered that,
      on macOS, windowState === window.STATE_MAXIMIZED for a short
      time when the window is first created. Then it rapidly changes
      to windowState === window.STATE_NORMAL. So I added a `setTimeout`
      promise to postpone checking the window size until after
      window creation "settles" and that seems to be enough to ensure
      we avoid showing the spurious notification box at window
      creation.
      
      Also fixes Bug 22543, "Tor Browser 7.0 shows window
      resize warning on every new window for a few seconds". And
      fixes issues raised in comments 2 and 3 in that ticket as well.
      97380447
  23. 04 Aug, 2017 2 commits
  24. 03 Aug, 2017 1 commit
  25. 01 Aug, 2017 1 commit
  26. 10 Jul, 2017 2 commits
  27. 24 Jun, 2017 1 commit
    • Kathleen Brade's avatar
      Bug 18913: about:tor should not have chrome privileges · 32f9cf56
      Kathleen Brade authored
      Rearchitect our implementation so that about:tor pages are always
      loaded in a content process. This also fixes:
        Bug 22535: Searching brings me to duckduckgo but my query is discarded.
        Bug 21948: Going back to about:tor page gives "Address isn't valid" error.
      
      Most of the code that initializes and updates about:tor content has
      been moved to a content script. When necessary, IPC is used to pass
      data from the chrome process to the content script.
      
      Removed old, no-longer-used m_tb_orig_BrowserOnAboutPageLoad variable
      from torbutton.js.
      
      Also, update the about:tor newChannel() implementation to accept an
      nsILoadInfo parameter.
      32f9cf56
  28. 16 Jun, 2017 1 commit
    • Georg Koppen's avatar
      Bug 22560: Update privacy.thirdparty.isolate preference · b917b202
      Georg Koppen authored
      In commit 2978978e we hinted at updating
      `privacy.thirdparty.isolate` once we switch to ESR 52. We forgot that
      while migrating but replace it now with `privacy.firstparty.isolate` as
      expected.
      
      We remove `dom.workers.sharedWorkers.enabled` as this preference is long
      gone.
      b917b202
  29. 12 Jun, 2017 1 commit
  30. 09 Jun, 2017 1 commit