If "Automatically enable all new beta features" is checked in [[Special:Preferences#mw-prefsection-betafeatures]] and you de-enable one or more beta features and save, the features stay enabled.
They do de-enable if you uncheck "Automatically enable all new beta features" but then you miss this feature. I am sure it wasn't working like that.
At this moment it is not enabling all new beta features but all of them.
[copied the better description from merged 186439]
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| mediawiki/extensions/BetaFeatures | master | +43 -16 | Visually signal that the auto-enrolled featured are set that way |
Yes, with a clean test account, but I've narrowed it down:
This is only a problem if "Automatically enable all new beta features" is also checked.
Plus it effects most other BetaFeatures, such as "New filters for edit review", but not all BetaFeatures (at testwiki, the exceptions are "Page previews" and "New wikitext mode".) I'll accordingly remove the CodeMirror tag here.
I've been able to reproduce as well, on enwiki prod.
Steps to reproduce:
I'm experiencing this myself, a user on WP:VP/T reported it too (see the dupe), and now another report on WP:HELPDESK.
https://en.wikipedia.org/wiki/Wikipedia:Help_desk#Help_me_disable_Beta_Feature:_Wikitext_syntax_highlighting
This likely also will affect the amount of beta users we have participating in experiments, since people might not be eager to re-enable "Automatically enable all new beta features" after this.
The logic for autoenrollment is here:
https://github.com/wikimedia/mediawiki-extensions-BetaFeatures/blob/1eb308f3c884ebe0325beff0a212f79ff69f0599/BetaFeaturesHooks.php#L224
Basically, if autoenroll influences this, then it seems to me that the value of the preference is not HTMLFeatureField::OPTION_DISABLED and not HTMLFeatureField::OPTION_ENABLED when being queried (aka not '1' or '0').
Another option could be that master/slave lag influences something here ?
If I understand correctly... I think T62747: BetaFeatures: Clicking "Automatically enable ..." should also activate all existing available BetaFeatures was accidentally (?) implemented at some point? Except that it currently takes a single preferences-save for it to reload the page and thus be visible to the user. I.e. to fix it completely: clicking the checkbox should immediately result in all the other checkboxes being marked.
It was discussed back in the feature's early days at https://www.mediawiki.org/wiki/Talk:Beta_Features/Archive_1#Enable_all_features where we concluded that it should do this, and also that we should change the wording of the checkbox's label from
"Automatically enable all new beta features"
into
"Automatically enable all current and new beta features"
to make it explicit.
This is acting as intended, yes, but the interface does indeed suck.
Having some JS to tick and disable all the relevant checkboxes for you would be good, agreed.
Most complicated is that it doesn't "Automatically enable all current and new beta features" – it won't enable features that are marked as never-auto-enable.
Wait, I'm an idiot. These are now ButtonInputWidgets, so for the PHP side of things we can "just" call #setLabel() on them. Doesn't get us to an API, however.
I'm facing this issue for quite some time now. I am getting a little frustrated by the inability to disable a beta-feature without having to turn-off "Automatically enable all new beta features". I find this frustrating as I do not like to turn-off "Automatically enable all new beta features" just to disable an existing beta feature as I might forget to enable "Automatically enable all new beta features" back again and might possibly miss a new beta feature just as @TheDJ mentions in his comment.
This is an irritating bug to encounter. It's counter intuitive to say "Automatically enable all new beta features" but imply "Automatically enable all beta features". Not to mention that the UI makes you think you disabled a beta feature, only to have it auto-re enabled.
Personally, I think this makes little sense. I usually like most beta features and want them auto-enabled. But I absolutely hate "New wikitext mode", so want it disabled. This current way guarantees I will not be enabling most/any beta features in the future.
To me, the ideal functionality should be "Automatically enable all new beta features". Anything currently unchecked will remain unchecked. Any new beta features added will be auto-enabled.
Here's what I think is a sensible thing to do: If a user unchecks a beta feature, then we should automatically uncheck the "Automatically enable all new beta features" checkbox. If they check it, all the checkboxes become checked again.
Here's what I think is a sensible thing to do: If a user unchecks a beta feature, then we should automatically uncheck the "Automatically enable all new beta features" checkbox. If they check it, all the checkboxes become checked again.
That sounds sensible only if the checkbox is labelled as "Automatically enable all beta features" instead of "Automatically enable all new beta features" as @Soni points out.
That sounds sensible only if the checkbox is labelled as "Automatically enable all beta features" instead of "Automatically enable all new beta features" as @Soni points out.
Plus, I think the checkbox should be "new features" and not "all features". Because there's no reason why someone should be opting out of all future beta features only because they find one of them unworkable. Logically, it makes sense for the checkbox to consider all future beta features, not all beta features ever.
Change 502643 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[mediawiki/extensions/BetaFeatures@master] Visually signal that the auto-enrolled featured are set that way
Change 502643 merged by jenkins-bot:
[mediawiki/extensions/BetaFeatures@master] Visually signal that the auto-enrolled featured are set that way