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

Ok, so now  we've come full circle.

Paraphrasing...
1. Tab: You can't drop prefixes without going to CR, so we want to get to CR.
2. Sylvain: But other stuff in the module containing gradients is not CR, so that holds up gradients from going unprefixed.
3. Elika: No it doesn't; features can go unprefixed at different rates in the same module.
4. Tab: You only need a test suite and implementation report to remove your implementation's prefix.
5. Boris: Before the spec has gone CR?
6. Tab: No, it still needs to be in CR.


So back to my original question:


   <florian> I agree with Fantasai's approach in general, but for this
             particular case, I would side with Sylvain, so that we can drop
             prefixes on gradients as soon as possible
   <fantasai> Florian, a feature that's not gradients will not hold back
              prefixes on gradients.
   <fantasai> Florian, prefixes are dropped per feature, not per module.


This is news to me.  Can you explain how this works?  Do sections (and subsections) get tagged with "CR" individually in the WD (or LC) document?




> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On
> Behalf Of Tab Atkins Jr.
> Sent: Thursday, August 18, 2011 7:52 AM
> To: Boris Zbarsky
> Cc: www-style@w3.org
> Subject: Re: Unprefixed properties and modules - RE: [CSSWG] Minutes
> and Resolutions Telecon 201-08-17
> 
> On Thu, Aug 18, 2011 at 5:37 AM, Boris Zbarsky <bzbarsky@mit.edu>
> wrote:
> > On 8/17/11 7:22 PM, Tab Atkins Jr. wrote:
> >> The idea is any implementation may drop prefixes as soon as they
> >> believe they pass the testsuite sufficiently.
> >
> > And before the module has entered CR?
> 
> No, it still needs to be in CR.  The idea was that we make it slightly
> harder to drop prefixes (only slightly - the browser gets to decide if
> they pass it "sufficiently", they just have to send an implementation
> report to the list justifying the decision), but simultaneously make
> it easier for individual features to lose their prefixes when the
> whole module hasn't yet been implemented.
> 
> 
> > How do we event determine that the test suite _exists_ sufficiently?
> This
> > last should be a WG decision, right?
> 
> I don't think that's been discussed, but probably, yeah.
> 
> ~TJ
>

Received on Thursday, 18 August 2011 17:04:42 UTC