3 ms·
For what it's worth, I don't dispute at all that the quality of CSS specs from the W3C has improved over time. However, specs are means to an end, and the usefu
by Silhouette 11y ago
For what it's worth, I don't dispute at all that the quality of CSS specs from the W3C has improved over time. However, specs are means to an end, and the usefulness of any spec is inevitably dictated by the implementations that exist.
As a professional, I truly wish this weren't the case, but as a professional, my job is to make a working site, not necessarily a standards compliant one. All too frequently, it is still not possible to do both at the same time, either because browsers don't implement W3C recommendations consistently, or because of the poor quality of implementation you alluded to yourself, or because even when browsers did provide a useful implementation yesterday someone broke it in an update last night and today I'm rewriting something a different way because platinum support customers started calling first thing this morning and get a same day response not a 6 week one.
"Of course I understand that it's the update we just rolled out to our corporate standard browser that broke your standards-compliant and otherwise normally functioning site," said no customer ever. :-)