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

Re: [CSSWG] Minutes and Resolutions Telecon 201-08-17

From: François REMY <fremycompany_pub@yahoo.fr>
Date: Thu, 18 Aug 2011 17:23:14 +0200
Message-ID: <DD6B56FBF048412F8A3FBF83F3667460@FREMYD2>
To: "Sylvain Galineau" <sylvaing@microsoft.com>, "fantasai" <fantasai.lists@inkedblade.net>, <www-style@w3.org>
+ -----Message d'origine----- 
+ From: Sylvain Galineau
+ Sent: Thursday, August 18, 2011 4:24 PM
+ To: Francois REMY ; fantasai ; www-style@w3.org
+ Subject: RE: [CSSWG] Minutes and Resolutions Telecon 201-08-17
+ It's a reasonable concern, though I think it really depends on how we
+ define what the feature is. I think one can have, say, border-radius as
+ a stable feature while multiple backgrounds are being worked on as they
+ are orthogonal. Or box-shadow vs. border-radius. As long as the 'CR 
+ is set in the right place, it needn't be harmful to the spec or authors.

I agree. A "CR" logo behind some paragraphs that are known "frozen" could do 
the trick, most of the time. But if features completion level inside a same 
document vary (too) much, maybe is it worth splitting it into a "CR" version 
that contains already accepted properties and another version containing all 
the other properties. So that someone that looks for "things as they are 
now" can find the CR specification he want.

+ "...than a document which change every week and that mix proposals, drafts
+ and accepted properties" That pretty much describes HTML5 over the past 
+ years. Do authors hate it for being that way ?

Seriously, I don't know if "authors" do hate the HTML5 spec. At least, you 
have found one that does. Me.

To be clear, I never read the HTML5 spec correctly because it's such a waste 
of time. Seeking the ten features that are usable today among the thirthy 
that aren't is something I really hate. I prefer to read UA blogs speaking 
about features implemented in a specific browser. At least, it's effective 
and immediately testable. Many HTML5 algorithms in the spec will never be 
implemented anytime soon. By the time they will get implemented, many 
changes will have been introduced and you'll forgot what you learnt before.

And I don't even rise the question about 'which' HTML5 specification I 
should read. 
Received on Thursday, 18 August 2011 15:22:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:03 UTC