W3C home > Mailing lists > Public > www-style@w3.org > February 2011

RE: CSS Variables

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Wed, 9 Feb 2011 17:37:02 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: Tab Atkins Jr. <jackalmage@gmail.com>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, www-style list <www-style@w3.org>
Message-ID: <045A765940533D4CA4933A4A7E32597E2AB591ED@TK5EX14MBXC120.redmond.corp.microsoft.com>
[Boris Zbarsky:]
> The idea is to not put the experimental features out to a wide testing
> audience, thus limiting their use to experimental, non-production
> situations (because they will only work in browsers used by a few hundred
> thousand people at the most).
> 
> This setup gives authors a chance to try the feature out and report
> feedback without having to deal with pages that actually depend on the
> feature.

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 ?

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. What would be the vehicle for Firefox ? 

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).
Received on Wednesday, 9 February 2011 17:37:40 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:37 GMT