- 21 Sep, 2017 1 commit
-
-
Arthur Edelstein authored
(Also removes a dot from aboutTor.donationBanner.slogan)
-
- 15 Sep, 2017 1 commit
-
-
Arthur Edelstein authored
-
- 30 Aug, 2017 1 commit
-
-
Kathleen Brade authored
Improve the overview/summary comment in external-app-blocker.js.
-
- 29 Aug, 2017 1 commit
-
-
Georg Koppen authored
-
- 23 Aug, 2017 2 commits
-
-
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.
-
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.
-
- 04 Aug, 2017 2 commits
-
-
Georg Koppen authored
-
For compatibility with recent changes to our browser patch, change the external app blocker module so it implements the new nsIHelperAppWarningDialog interface. Since the external app blocker module is no longer a service, split the drag and drop filter into a separate component (which remains a service).
-
- 03 Aug, 2017 1 commit
-
-
Georg Koppen authored
-
- 01 Aug, 2017 1 commit
-
-
Automatically adjust the height of the Security Settings window so that no scrollbar is needed. Also, add 100 pixels to the width and increase maxheight and maxwidth to give users more flexibility when they choose to manually resize the window.
-
- 10 Jul, 2017 2 commits
-
-
Arthur Edelstein authored
-
Arthur Edelstein authored
-
- 24 Jun, 2017 1 commit
-
-
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.
-
- 16 Jun, 2017 1 commit
-
-
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.
-
- 12 Jun, 2017 1 commit
-
-
Georg Koppen authored
Mozilla made the Battery API chrome-only (https://bugzilla.mozilla.org/show_bug.cgi?id=1313580). We therefore don't need to take care of it anymore in Torbutton.
-
- 09 Jun, 2017 1 commit
-
-
Georg Koppen authored
-
- 08 Jun, 2017 1 commit
-
-
Kathleen Brade authored
Increase the height of the security slider description area to avoid a scrollbar on macOS 10.12 (previously, the text associated with the "High" level required a scrollbar).
-
- 02 Jun, 2017 4 commits
-
-
Georg Koppen authored
-
Georg Koppen authored
-
Fix problems with missing video playback controls and missing scrollbars. Use a regex solution to allow access to all png images, svg images, and css files under chrome://global/skin/media.
-
Georg Koppen authored
Instead of whitelisting single resources for view-source requests that might allow platform detection we allow all of those that are needed by requests with a view-source origin. This should be safe now that https://bugzilla.mozilla.org/show_bug.cgi?id=1172165 landed.
-
- 01 Jun, 2017 2 commits
-
-
Kathleen Brade authored
Avoid noise on the error console when a page is reloaded. Since 304 responses do not have Location headers, it is safe to ignore such responses inside our http-on-examine-response observer.
-
Kathleen Brade authored
Load our content policy module as a process script instead of as a component so that our nsIContentPolicy filter runs in content processes. Our http-on-examine-response code that blocks redirects to internal URLs must continue to run in the chrome process only.
-
- 13 Apr, 2017 3 commits
-
-
Georg Koppen authored
-
Georg Koppen authored
-
Georg Koppen authored
It turns out that the JIT *.content prefs are gone for a while now. This happened in https://bugzilla.mozilla.org/show_bug.cgi?id=939562 and the patch updates the security slider to take this into account. We got the tip to include `javascript.options.native_regexp` as well. `javascript.options.typeinference` is gone with https://bugzilla.mozilla.org/show_bug.cgi?id=972817 and we therefore remove it. And asm.js is disabled globally until we find a good solution for #19417. The tooltip text got updated accordingly.
-
- 07 Apr, 2017 1 commit
-
-
Georg Koppen authored
This reverts commit 1b7ce9f5. We did not backport Mozilla's patch which uses the new preference. Thus we need to stick to the old one for now. Closes #21885.
-
- 04 Apr, 2017 10 commits
-
-
Georg Koppen authored
-
Also, make sure we renew catchall "--unknown--" domain if user chooses "New Tor Circuit" for about:addons, for example.
-
-
-
Ignore "not available" errors from appCacheStorage.asyncEvictStorage() since these can occur if the cache has not been used yet. Change torbutton_close_tabs_on_new_identity() to use browser.removeTab() instead of browser.contentWindow.close() since we cannot directly access the contentWindow when multi-process mode is enabled. Fix indentation and modernize the torbutton_close_tabs_on_new_identity() code.
-
Georg Koppen authored
-
-
Also, use Cc, Ci, and Cr inside torbutton_resizelistener.
-
-
-
- 03 Mar, 2017 2 commits
-
-
Georg Koppen authored
Version bump, and CHANGELOG update
-
Georg Koppen authored
-
- 02 Mar, 2017 1 commit
-
-
Georg Koppen authored
-