- From: Christoph Päper <christoph.paeper@crissov.de>
- Date: Sun, 6 May 2012 23:38:53 +0200
- To: www-style list <www-style@w3.org>
Lea Verou: > On 5/5/12 16:18, Boris Zbarsky wrote: >> … the right solution is to not ship prefixed stuff in final releases … > > 1. It has been mentioned in this thread that it’s against company policy of several implementors. > 2. It defies the entire advantage that prefixes were supposed to bring: Getting author input for in-development features. The thing is that both parties don’t stick to the conditions of the deal, because of (possible) short-term benefits. It would be okay if vendors implemented first and proposed for standardization second, *iff* they were willing to change their implementation to match the evolving or final standard *and* drop support for their sunrise implementation at some point. It would be okay if authors used prefixed features, *iff* they considered and accepted that they will have to maintain the code as specifications and implementations evolve and they can guarantee to do so. PS: Prefixes that do not change are never okay to use to work around bugs in one browser or the other.
Received on Sunday, 6 May 2012 21:39:22 UTC