- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Thu, 18 Aug 2011 12:21:13 -0700
- To: www-style@w3.org
On 08/18/2011 10:04 AM, Brian Manthos wrote: > 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? http://lists.w3.org/Archives/Public/www-style/2011Aug/0522.html ~fantasai
Received on Thursday, 18 August 2011 19:21:51 UTC