1673487 - Make about:preferences#experimental ride the trains

Status: NEW

(Firefox :: Settings UI, enhancement)

Comment 1

[Neha Kochar [:neha]]

We would like to have this opt-in capability for Fission in Beta.

Comment 2

[Sebastian Zartner [:sebo]]

I guess that's worth a release note, right?

Sebastian

Comment 3

[Blake Winton (:bwinton) (:☕️)]

Well, a beta note, maybe, if we decide to do it… ;)

Comment 4

[Markus Jaritz [:markus] (UX)]

Having this in Beta might be OK, but I heavily recommend not moving this section to release.
Even for beta we should evaluate the impacts this can have on people's experience, and on the development of the features in that list.
Questions I am not aware of answer for regarding this:
How do we maintain that list to ensure it is always up to date?
How do we communicate about removing features from the list? (either to kill it, or have it become the new default)
How does being on the list impact experiments teams are running on those features? (Can we differentiate between user-activated and experiment-activated)

Comment 5

[Neha Kochar [:neha]]

(In reply to Sebastian Zartner [:sebo] from comment #2)

I guess that's worth a release note, right?

Yes, a beta note, when this lands.

Comment 6

[Neha Kochar [:neha]]

(In reply to Markus Jaritz [:designakt] (UX) from comment #4)

Having this in Beta might be OK, but I heavily recommend not moving this section to release.

Sure, only asking for Beta, not release.

Even for beta we should evaluate the impacts this can have on people's experience, and on the development of the features in that list.

This would be opt-in features where we can get some early feedback from users who are willing to help us. Since dev edition is based on beta, we can get a lot of help from web developers.

Questions I am not aware of answer for regarding this:
How do we maintain that list to ensure it is always up to date?

Same as we do for Nightly, I guess?

How do we communicate about removing features from the list? (either to kill it, or have it become the new default)

Will Beta new features notes suffice?

How does being on the list impact experiments teams are running on those features? (Can we differentiate between user-activated and experiment-activated)

This depends on the feature. Fission experiment, for example, excludes opted-in users.

Comment 7

[Chris Peterson [:cpeterson]]

(In reply to Neha Kochar [:neha] from comment #1)

We would like to have this opt-in capability for Fission in Beta.

Update: given the short time frame and open questions about showing the experimental features UI in late Beta and release candidate builds, we've decided that we won't use the experimental features UI for testing Fission in Beta.