| Commit message (Collapse) | Author | Age |
| |
|
|
| |
Disables the Windows Jump Lists by disabling the associated prefs.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a result of 28507. The new logic caused the stack trace:
: *************************
: A coding exception was thrown and uncaught in a Task.
:
: Full message: TypeError: Cc['@mozilla.org/push/Service;1'] is undefined
: Full stack: Sanitizer.prototype.items.siteSettings.clear</<@resource://gre/modules/Sanitizer.jsm:128:15
: Sanitizer.prototype.items.siteSettings.clear<@resource://gre/modules/Sanitizer.jsm:127:15
: TaskImpl_run@resource://gre/modules/Task.jsm:326:42
: TaskImpl@resource://gre/modules/Task.jsm:275:3
: asyncFunction@resource://gre/modules/Task.jsm:247:14
: _clear@resource://gre/modules/Sanitizer.jsm:59:14
: clearItem@resource://gre/modules/Sanitizer.jsm:40:14
: sanitize@chrome://browser/content/browser.js:1566:25
: onEvent@chrome://browser/content/browser.js:1787:9
:
: *************************
|
| | |
|
| |
|
|
| |
installed
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Prior to this patch, TBA was showing onion services as insecure
connection and SSL/TLS ones as encrypted connections(lock icon).
This patch fixes the issue adding several new onion icons to indicate
all the various permutations of onions services hosted HTTP or HTTPS
pages.
|
| |
|
|
| |
This allows for notifications on all supported versions of Android.
|
| | |
|
| |
|
|
|
| |
If the user swips away the app, then initiate quitting as if the user
selected Quit from the menu.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We are not ready for that yet.
This reverts commit 8e8445c1d47644e6e34fc1b96d6934a9aa13f58b.
|
| |
|
|
|
|
|
|
| |
When the TBA is forcefully closed, its private data is not deleted,
even if the history.clear_on_exit is set.
As fallback, this patch calls the Sanitize:ClearData event in the
browser startup to clean the private data if needed.
|
| |
|
|
| |
default
|
| |
|
|
|
|
|
|
| |
Android allows a set of String values in the preferences editor.
However, the TBA distribution just supported simple scalar types.
This patch implements the code to parse complex prefs from the
distribution preference file.
|
| | |
|
| |
|
|
| |
Revert changed localized string we don't use anymore.
|
| | |
|
| |
|
|
|
|
|
|
| |
- Add preferences.json: it is used to configure android specific
preferences
- Keep the ActivityStream HomePager closed when the user clicks in the
url bar
|
| |
|
|
|
|
| |
This allows highlighting/selecting text by long pressing.
Thanks to towiw for the info.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes:
* File menu:
- Save Page As
* Context menu in content pages:
- Save Page As
- Save Image As
- Save Video As
- Save Link As
- Save Frame As
* Page Info "Media" Panel:
- Save As
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Because of the non-restartless nature of Torbutton, it required
a two-stage installation process. On mobile, it was a problem,
because it was not loading when the user opened the browser for
the first time.
Moving it to tor-browser and making it a system extension allows it
to load when the user opens the browser for first time.
Additionally, this patch also fixes Bug 27611.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Large pdf files download in parts via range-based requests so that users
can begin reading before the entire file has finished downloading. This
is implemented using XMLHttpRequests. However, since these requests are
created in the chrome, they are given the System Principal and lack the
correct firstPartyDomain associated with the parent window.
This patch manually sets the XMLHttpRequest's originAttributes to the
one provided by the real owning window cached in the RangedChromeActions
object. This is done via the chrome-only setOriginAttributes method.
The method is called in the xhr_onreadystatechanged() callback rather
than directly after construction in getXhr() because the
setOriginAttributes implementation requires the internal nsIChannel
object to have been created but not used. Fortunately, the
XMLHttpRequest object fires the readStateChangedEvent precisely after
the channel has been created in the XmlHttpRequest's Open() method.
The nsIChannel's nsILoadInfo's OriginAttributes are now overwritten
with the known OriginAttributes of the parent window before anything
else has had a chance to use it.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
r=JanH
E.g. autocompletion results and the "Recently closed" list.
|
| |
|
|
| |
TabsLayoutItemView. r=JanH
|
| |
|
|
| |
r=JanH
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a=pascalc
Reviewers: dimi
Reviewed By: dimi
Subscribers: dveditz, francois, dimi
Bug #: 1441345
Differential Revision: https://phabricator.services.mozilla.com/D5479
--HG--
extra : source : 3fa9372e4c5f05713fe1a9f758487fa443ce7500
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
if it navigates to a view-source URL r=asuth
The suppressing of the error NS_ERROR_UNKNOWN_PROTOCOL will break the
web-platform-test 'windowclient-navigate.https.html' since navigating
to an invalid view-source url through the client API won't receive
any error due to the suppressing. So the test will time-out since it
waits for an error.
While navigating to an invalid view-source url with its inner url as
relative, this will pass the validity check we have right now and
do the navigation because of it takes account the baseURL while doing
the check. The invalid view-source url will be resolved into a valid
view-source url in the case. Fortunately, we won't encounter any issue
in the test in the past since the docShell will block this loading
because it's loading a view-source url inside an iframe and reports a
NS_ERROR_UNKNOWN_PROTOCOL error. But, we should faild with a
NS_ERROR_MALFORMED_URI error when doing the URL validity check.
For addressing this, this patch makes the client.navigate to not take
the baseURL into account if it is a view-source URL.
Differential Revision: https://phabricator.services.mozilla.com/D6587
--HG--
extra : moz-landing-system : lando
|
| |
|
|
|
|
|
|
|
|
|
|
| |
loading an unknown protocol. r=smaug
This test case will try to navigate an iframe to an unknown protocol and
check whether no errors been reported.
Differential Revision: https://phabricator.services.mozilla.com/D3493
--HG--
extra : moz-landing-system : lando
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
external protocol. r=smaug
This patch makes the docshell not to report an error if it is a unknown
protocol error. However, we will still display the error page in this
case.
Differential Revision: https://phabricator.services.mozilla.com/D3492
--HG--
extra : moz-landing-system : lando
|
| |
|
|
|
|
|
| |
Don't bind --enable-release to MOZILLA_OFFICIAL for Windows targets as
we are currently crashing on start-up for unknown reasons if
--enable-release is set, see:
https://bugzilla.mozilla.org/show_bug.cgi?id=1470772.
|
| |
|
|
|
| |
This fixes a problem where some preferences had the wrong default value.
Also see bug 27472 where we made a similar fix for Android.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Child content processes require certain directories to be marked as
readable or writeable when Sandboxing is enabled. The directories
to be whitelisted are saved in static variables in
sandboxBroker.cpp and are initialized in
SandboxBroker::GeckoDependentInitialize(). Any child content process
which is created before these directories are saved will be unable to
read or write to them.
The tor-launcher extension triggers the creation of a content process
which hosts the tor network configuration settings window. This process
is created before the whitelisted directories are saved. The network
settings process doesn't need access to these directories to function,
but subsequent content processes which are created once the settings
window exits do need these directories to function. Sometimes, the
creation of these subsequent processes is slow enough for the parent
process to 'catch up' and create the whitelist resulting in the broken
about:tor tab or broken white tab.
A previous iteration of this patch moved the GeckoDependentInitialize()
call directly above the call to DoStartup(). However, Mozilla dev Bob
Owen objected to this since this places the call before various
services are initialized which the SandboxBroker may depend on. Some
experimentation would seem to confirm his objections: placing the
whitelist init just prior to DoStartup() results in an empty value for
the profile directory which prevents child processes reading the chrome
and extensions directory.
This patch inserts the GeckoDependentInitialize() call into DoStartup()
just after the profile directory is known and queryable by the
SandboxBroker, and before the 'profile-after-change' notification is
fired. It also reverts the temp fix which reduced the sandbox level to
2 on windows.
|
| |
|
|
|
|
|
|
|
|
| |
In Tor Browser 8.0, the OS was revealed in both the HTTP User-Agent
header and to JavaScript code via navigator.userAgent. To avoid
leaking the OS inside each HTTP request (which many web servers
log), always use the Windows 7 OS value in the desktop User-Agent
header. We continue to allow access to the actual OS via JavaScript,
since doing so improves compatibility with web applications such
as GitHub and Google Docs.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
within a javascript: URL. r=snorp
MozReview-Commit-ID: DzE0UJfMcCI
--HG--
extra : rebase_source : 2a9bcc74447a8a2862aa3c753f7bd30e1d0361dc
|
| |
|
|
|
|
|
| |
Our workaround for bug 26520 does not work for Windows users as
on Windows WebExtension background scripts are running in a different
process. To get Tor Browser 8 out we disable the separate process for
the time being while working on a better fix.
|
| |
|
|
|
|
|
|
| |
browser is stuck in endless reload cycle
The problem goes away when the security.sandbox.content.level pref is
set to 2. This patch sets the option on Windows only to work around
this issue until the root cause is found and fixed.
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
When privacy.spoof_english === 2, then en-US spoofing is enabled.
In that case, make sure the date picker does not leak the locale.
|