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

Unfortunately I find this more confusing rather than less confusing.

To simplify...

A. We have a module at WD.
B. Some of the module is ready to be unprefixed.
C. The rest of the module is not ready to be unprefixed.

How do you get to...
   1. The feature is in CR.
... for the features in B, while respecting the C constraint.

-----Original Message-----
From: [] On Behalf Of fantasai
Sent: Thursday, August 18, 2011 12:14 PM
Subject: Re: [CSSWG] Minutes and Resolutions Telecon 201-08-17

On 08/17/2011 09:04 PM, Sylvain Galineau wrote:
> [fantasai:]
>>     - RESOLVED: Put ltr | rtl keywords back into image(), mark as at-risk.
> ...
>> <fantasai>  Florian, prefixes are dropped per feature, not per module.
> Don't know how I missed this; the last time I pointed out we agreed we 
> could move to CR on a per-feature basis when possible you said we did 
> not in fact agree to that, though we discussed it. Can you point to 
> the decision allowing us to do this? If that is the case then we never 
> needed to move anything to Level 4 on the grounds of moving gradient standardization forward, did we ?

We did not agree to move to CR on a per-feature basis.
We did agree to allow prefix-dropping on a per-feature basis.

Dropping prefixes != moving to CR.

Dropping prefixes requires:
   1. The feature is in CR.
   2. The implementation is correct *per CR spec*
   3. The implementation proves its correctness via tests.

It's possible for #1 to be true for features that don't satisfy all three.



Received on Thursday, 18 August 2011 20:15:21 UTC