Are you serious? Maybe the majority of users don't have userContent.css customizations. But a significant minority do. And consider who evangelizes firefox. You guessed it. It's the power users. Take that away and there's very little reason for any user to pick Firefox over Chrome. Mozilla is losing ground and they can't figure out why and your post shows what the problem is. If Mozilla goes out of their way to alienate users like me (and the GP), they're going to slide into irrelevance.
There has NEVER been a "significant minority" using userContent.css. Never. I'm sure there is the odd person who uses it, maybe to override some annoying font or for their own needs but that's it. That doesn't mean it should be removed because it should be trivial to implement and test ("if userContentFile.exists() { loadCSS(userContentFile); }" but perspective.
userContent.css (Score:3, Insightful)
Mozilla can just fuck right off. They're pulling this shit at the same time they're planning on removing userContent.css support.
Re: (Score:2, Funny)
OMG what are you and, well literally no-one else, going to do that happens?
Re: (Score:4, Insightful)
Are you serious? Maybe the majority of users don't have userContent.css customizations. But a significant minority do. And consider who evangelizes firefox. You guessed it. It's the power users. Take that away and there's very little reason for any user to pick Firefox over Chrome. Mozilla is losing ground and they can't figure out why and your post shows what the problem is. If Mozilla goes out of their way to alienate users like me (and the GP), they're going to slide into irrelevance.
Re:userContent.css (Score:2)