Loading a website and then trying to download it via the "Save as..."-option in the context menu results in the catch-all circuit being used. This is new with the switch to ESR52.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Loading torproject.org and doing a right-click and choosing "Save Page As..." gives me a ton of errors like:
[06-07 13:02:38] Torbutton NOTE: tor domain isolator error: channel.loadInfo is nullloadInfo is null for channel https://www.torproject.org/images/military.jpgHandler function threw an exception: TypeError: channel.loadInfo is nullStack: NetworkMonitor.prototype._createNetworkEvent@re[/gre/modules/commonjs/toolkit/loader.js](/gre/modules/commonjs/toolkit/loader.js) -> re[/devtools/shared/webconsole/network-monitor.js:1077:9](/devtools/shared/webconsole/network-monitor.js:1077:9)NetworkMonitor.prototype._onRequestHeader@re[/gre/modules/commonjs/toolkit/loader.js](/gre/modules/commonjs/toolkit/loader.js) -> re[/devtools/shared/webconsole/network-monitor.js:1154:5](/devtools/shared/webconsole/network-monitor.js:1154:5)NetworkMonitor.prototype.observeActivity<@re[/gre/modules/commonjs/toolkit/loader.js](/gre/modules/commonjs/toolkit/loader.js) -> re[/devtools/shared/webconsole/network-monitor.js:1014:7](/devtools/shared/webconsole/network-monitor.js:1014:7)exports.makeInfallible/<@re[/gre/modules/commonjs/toolkit/loader.js](/gre/modules/commonjs/toolkit/loader.js) -> re[/devtools/shared/ThreadSafeDevToolsUtils.js:101:14](/devtools/shared/ThreadSafeDevToolsUtils.js:101:14)Line: 1077, column: 9
and it does not download anything (while default 7.0 at least downloads the website) I built a custom build with the patch in comment:5 applied on top. But that was the only difference to our usual nightly builds.
Trac: Status: needs_review to needs_revision Keywords: TorBrowserTeam201706R deleted, TorBrowserTeam201706 added
Sorry for these errors. I think I have fixed this problem and made some other improvements. Here's a new version for review, rebased on top of the latest tor-browser 7.5 branch:
There's something broken with the "Save Link As..." contextual action, as well:
It, also, ends up over the catch-all circuit.
Furthermore, "sometimes" Tor Browser's custom "Save external file type?" dialog is not shown, instead Firefox's "Save As" dialog is shown directly. When this happens, after confirming said "Save As" dialog, the download is not started ("nothing happens", as they say). I have not yet discovered a reliable way of reproducing this but it's not rare, it occurs after trying a few times with random links.
I have not (yet) seen these problems occur when following the link instead.
There's something broken with the "Save Link As..." contextual action, as well:
It, also, ends up over the catch-all circuit.
Yes. We might want to outsource that one to an own ticket as the external helper app dialog is involved and we had a bunch of trouble with that piece while transitioning to esr52. I created #22649 (moved).
Furthermore, "sometimes" Tor Browser's custom "Save external file type?" dialog is not shown, instead Firefox's "Save As" dialog is shown directly. When this happens, after confirming said "Save As" dialog, the download is not started ("nothing happens", as they say). I have not yet discovered a reliable way of reproducing this but it's not rare, it occurs after trying a few times with random links.
Sorry for these errors. I think I have fixed this problem and made some other improvements. Here's a new version for review, rebased on top of the latest tor-browser 7.5 branch:
This breaks the Save Image As... option. Currently, that one is at least working even though the catch-all circuit is getting used. But with your patch I get
Full message: TypeError: aInitiatingDocument is nullFull stack: continueSave@chrome://global/content/contentAreaUtils.js:467:1internalSave/<@chrome://global/content/contentAreaUtils.js:446:7Handler.prototype.process@re[/gre/modules/Promise.jsm](/gre/modules/Promise.jsm) -> re[/gre/modules/Promise-backend.js:932:23](/gre/modules/Promise-backend.js:932:23)this.PromiseWalker.walkerLoop@re[/gre/modules/Promise.jsm](/gre/modules/Promise.jsm) -> re[/gre/modules/Promise-backend.js:813:7](/gre/modules/Promise-backend.js:813:7)this.PromiseWalker.scheduleWalkerLoop/<@re[/gre/modules/Promise.jsm](/gre/modules/Promise.jsm) -> re[/gre/modules/Promise-backend.js:747:11](/gre/modules/Promise-backend.js:747:11)
. I guess it might be worth addressing the catch-all-circuit-issue for the image saving part while we are at it.
Trac: Keywords: TorBrowserTeam201706R deleted, TorBrowserTeam201706 added Status: needs_review to needs_revision