Comment 345 for bug 1575053

I have to agree with Hadmut that if the team is so small and busy with other things that it hasn't been able to address a high-importance bug that's causing a disturbance for users in nearly 7 years, then it seems that the decision to make it a default was premature. Is there any way the team can back-pedal on that decision until the team is more prepared?