Comment 25 for bug 1960758

When I see a new config file option being added already in a deprecated state, I have to wonder if it's the right fix: "NEW config file option! But it's deprecated, please try not to use it" :)

If we need a workaround, maybe it shouldn't be in the config file like that. It's opt-in, the default value is such that it doesn't change behavior, sounds like the config file is just a means for documentation. If this is indeed the only way to address this, could it not be in the default config file, and perhaps just be a "hidden" option that will be honored in this version? Its documentation could be elsewhere.