- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Thu, 23 Feb 2012 03:52:35 +0000
- To: Christoph Päper <christoph.paeper@crissov.de>
- CC: "www-style@w3.org Style" <www-style@w3.org>
[Christoph Päper:] > > Sylvain Galineau: > > I don't see how such a scheme helps authors. If each vendor supports a > > different stage of a spec they'll still end up with a bunch of prefixed > versions of the same thing. > > Actually, Web authors shouldn't be using any prefix, except for '-draft-' > maybe. Authors shouldn't do a lot of things. But they do them. With abandon. Any solution that presupposes people won't do the things they're not supposed to do is somewhat doomed. When it's something they've already been accustomed to doing for years, it sounds like a bad assumption. But assuming no one - or almost no one - would use them, I'm not quite sure why implementors would bother with any of those prefixes in the first place? > > Browsers, however, could use the other prefixes to allow access to > specific states of implementation for testing and usage in controlled > environments (i.e. intranets). The draft prefix would be an alias to the > most stable or conforming one. I'm not sure what you mean by 'controlled'; if it can be accessed by the author without the user's help then experience shows there really is no such thing as a controlled environment.
Received on Thursday, 23 February 2012 03:53:14 UTC