Bundle our custom prefs into the Tor Browser's omni.ja (refs: #15023)
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.
Showing with 57 additions and 3 deletions
config/chroot_local-includes/etc/tor-browser/profile/user.js → config/chroot_local-includes/usr/share/tails/tor-browser-prefs.js