- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 09 Feb 2011 12:44:19 -0500
- To: Sylvain Galineau <sylvaing@microsoft.com>
- CC: "Tab Atkins Jr." <jackalmage@gmail.com>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, www-style list <www-style@w3.org>
On 2/9/11 12:37 PM, Sylvain Galineau wrote: > So what I am missing is that these do not make it into public releases, > Betas and other bits generally downloaded by large populations so that > web authors cannot rely on them in their pages ? Correct. That's why Tab mentioned putting it into the dev channel, but not the beta channel for Chrome. > In the case of IE, Previews are actually downloaded by large samples > but I'd assume they qualify since they have no chrome and really > targeted at developers. Seems reasonable. > What would be the vehicle for Firefox ? Nightly builds. > I'm still not quite sure I like the idea of releasing experimental features > completely unmarked as such - i.e. they look, smell and act like 'real' > features - and then pull them out later. I would suggest some kind of > explicit opt-in in the stylesheet letting the author declare 'yes, turn > on the experimental stuff for browser X'. At a minimum it'd help spot the > problem when such pages make it to the public web and someone reports a bug > against them (you can count on that happening). Sure; that seems like a problem for the particular UA doing the experimenting, to be solved however it wishes, right? -Boris
Received on Wednesday, 9 February 2011 17:45:23 UTC