Add a checkbox to enable the connect assist experiments on alpha
For S96 we're doing a lot of work, but we want to gate it somehow.
Initially we thought of gating it to nightly, which isn't ideal because nightly has also all the various Moz experiments, which probably make it easy to tell from alpha and form release (can we schedule #41989 pretty please?
So, the second idea we had is to add an opt-in in alpha.
We talked of a checkbox in #tor-browser-dev, but I think there's some misunderstanding of where the efforts are going.
Right now, only the legacy tor daemon works in our builds.
There are two developments effort:
- firefox-android!48 (merged), which is in part built on top of the legacy daemons, in part no-op
-
!852 (merged), which is working on the backend, but once merged will enable the bootstrap independently of the legacy daemons (almost, it'll use the file they provide). Since we don't have a frontend for it, we've enabled
about:torconnectalso on Android, and I've written some CSS to make it look like the Android version we'll have.
Eventually, the native UX will replace about:torconnect, but until that happens, I think we should allow users to use about:torconnect.
So, I'm not sure a checkbox will be okay. We might have 3 states:
- legacy bootstrap (which should also be the default)
- about:torconnect (to allow us to test the backend and possibly the settings - #42301 (closed))
- the new native UX (which also hasn't been merged)
Big warning: !852 (merged) updates the proxy preferences. In addition to changing the frontend, changing opting in/out of the new experience, should reset the proxy preferences. This needs some plumbing, but it's a pref, so we know how to implement it quite easily.