GitLab

… otherwise it appears as "Tor Browser" in the taskbar.

I did not manage to make it robust enough with Firefox 60 and this test was
never meant to exercise the HTML5 player: it was introduced
(commit:136db50c) to ensure our AppArmor
confinement for Tor Browser did not break audio playback, so let's
do this and not more, just like we're doing for the video test as well.

… and factorize a bunch of lines in passing.

I did not manage to prevent the omnibar from allowing search
so let's simply delete the search plugins, which is the same,
from an end-user perspective, as before: we hid the search bar
via userChrome.css.

I'm not removing this one-liner in userChrome.css though, just in case it's
re-enabled by default at some point via Tor Browser prefs or something.

AppArmor: give the Tor Browser "Web Content" process access to the system-wide webext directory (refs: #15717)

… otherwise uBlock cannot be loaded once we confine these processes under their
own AppArmor profile.

Confine Firefox 60 "Web Content" processes under the torbrowser_plugin_container AppArmor profile (refs: #15716)

It causes this error:

  ERROR: ld.so: object 'libmozsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

… presumably because LD_LIBRARY_PATH is not set due to the "P" profile
transition flag.

Initially it says "Search or enter address" and after some actions it says
"Search with DuckDuckGo or enter address", both in Tor Browser, Unsafe
Browser, and Tor Browser 8.0a9 outside of Tails.

… otherwise the "Watching a WebM video" test fails ("No video with supported
format and MIME type found.") and I see this in the Journal:

  Jul 04 09:25:39 amnesia tor-browser.desktop[9040]: [Child 9313, MediaPlayback #3] WARNING: Decoder=7e6a6a774200 state=DECODING_METADATA Decode metadata failed, shutting down decoder: file /var/tmp/build/firefox-a0efd2fcd6e9/dom/media/MediaDecoderStateMachine.cpp, line 379
  Jul 04 09:25:39 amnesia tor-browser.desktop[9040]: [Child 9313, MediaPlayback #3] WARNING: Decoder=7e6a6a774200 Decode error: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006): file /var/tmp/build/firefox-a0efd2fcd6e9/dom/media/MediaDecoderStateMachine.cpp, line 3445

We already had to bump the number of vCPUs to 2 for the exact same reason.
I suspect that increased e10s usage has something to do with it.

I can't reproduce the bug and that video plays just fine with only 2 vCPUs on
a manual testing VM of mine, so I'll call this a test suite only issue.

It's hard to test in the context of the local proxies settings scenario with
Firefox 60 and it's somewhat orthogonal to that scenario (except as an
"anti-test"). Let's test it separately and explicitly.

… and incidentally, this image can be used by future tests of other GTK3 apps.

Mixing Dogtail and Sikuli is tricky: in this case, Dogtail pretended it had
clicked the Print button, but that was before the output file selection dialog
had disappeared, so that click did nothing. So let's do the same as in the
Evince test, that works in a robust manner.

That's the standard GTK3 print button, not a specific Evince one.

These strings are now managed in po/*.po + Transifex.

This does not address the main problem (the name of the app in the taskbar)
but it's a start.

I see it succeed too fast, presumably because the Reload button is displayed for
a little bit, after pressing Enter, before it's replaced by the Stop button
while the page is loaded, and finally reappears.

It now uses the system GTK3 dialog.

It's actually the same dialog for all GTK3 apps and e.g. Tor Browser 8
can now reuse it.

Test suite: take into account that the Reload button now looks different in the Unsafe Browser than in Tor Browser (refs: #15023)

It has the red theme applied.

For some reason, it's ignored when we set it via
/usr/share/tails/tor-browser-prefs.js.

This probably won't be enough to fix #15706 ("Tor Browser 8 always prompts wrt.
asking webpages in English") until
https://trac.torproject.org/projects/tor/ticket/26409 is fixed.
But once Torbutton is fixed, then this should avoid Firefox prompting
the user.

It now works just fine with Firefox ESR60.

Cherry-picked from
https://github.com/micahflee/torbrowser-launcher/commit/ad95bbda69045f3c9ace241939ee9e1fccc16ac8

This code resets browser.uiCustomization.state, intl.locale.matchOS
and other stuff, which can be greatly confusing when working
specifically in this area of our Tor Browser customization.

pref() is not honored in prefs.js.

The Tor check done by Torbutton now works fine, no need to disable it anymore.

Shipping them in user.js has a few downsides:

 - They override whatever is in prefs.js so basically prefs in user.js are
   locked:  any modification done in about:config will be reverted next time Tor
   Browser starts, which can be a PITA when developing Tails.

 - In about:config, all these prefs are listed as modified by the user,
   which feels wrong.

 - It makes it harder for derivatives to implement things properly.