The problem with prefixes is that they are supposed to go away.
Why do I want stuff that is "supposed to go away" in my code?
I'd rather just "not have it in the first place".
Why do I want stuff that is "supposed to go away" in my code?
I'd rather just "not have it in the first place".
However, this is a way for a browser vendor to test their code in real life. If it fails, they can change the prefix and try again till they get it right. You can't do that once it's standardized. In fact, there are a number of properties that have been implemented incorrectly and still exist today but were eventually fixed in the non-prefixed property.
But a developer is to then remove the prefixed property. Not complain about it and blame others for their decision to use it in the first place.
Because you want the functionality that it gives.
Syntax and behavior of css changed between proposals and early drafts of a new feature and the final result.
So without prefixes you'd have a single "XXX" CSS name that might get deprecated altogether (eg the name ends up XXY) or be defined to have different behavior (e.g. it remains XXX, but not it also makes the element bold rather than just italic).