- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Sat, 25 Jun 2016 13:06:12 +0000
- To: public-css-archive@w3.org
We've been over this multiple time, so I know you don't like it, but the reason in favor it such things is always the same. If the web platform depends on something, regardless of how ugly its name is, we're stuck with it. Bad names that we can remove should be, but if the web depends on it enough that browsers feel they must add it / cannot remove it, then it doesn't help anyone to pretend it's not part of the platform. The web has its fair share of warts. Some bad names come from haphazard naming back when it was invented, and some come from our unfortunate history with prefixes. Regardless, if we're stuck with them, we're stuck with them. We've already decided for other properties to include in the canonical spec the ugly prefixed de-facto name, and I think we should stay consistent with that. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/237#issuecomment-228539626 using your GitHub account
Received on Saturday, 25 June 2016 13:06:14 UTC