T168376 describes a mechanism for opting out of the New Filters UX (once the UX graduates out of beta on RC page). The New Filters beta, however, covers more than just RC page, since it also includes beta features that are (or will be) on Watchlist. We need to confirm that these two preferences are compatible with one another, in the following ways:
Users who opt IN to the beta but OUT of the graduated UX on RC page
After RC page graduation, New Filters beta opt-in users who select the "Hide the improved version of Recent Changes" preference will have the following experience:
- They will get the old UX on RC page. They will see NO new features (as described in T168376).
- The same holds true for Related Changes, which we are generally treating as a flavor of RC page.
- These users will, however, continue to get all beta features on Watchlist.
- (Selecting the "Hide the improved version of Recent Changes" option expresses no preference about a future version of Watchlist that has also graduated out of beta. When that happens, we will create a new opt-out for Watchlist.)
lf whoever takes this task confirms that the functionality currently is as above, we can close the task. If it's not, however, we should figure out what needs to be done and rewrite the task.