- From: Arron Eicholz <arronei@microsoft.com>
- Date: Mon, 9 Feb 2015 16:39:33 +0000
- To: "L. David Baron" <dbaron@dbaron.org>, Florian Rivoal <florian@rivoal.net>
- CC: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On Saturday, February 7, 2015 2:12 AM L. David Baron [mailto:dbaron@dbaron.org] wrote: > On Saturday 2015-02-07 18:41 +0900, Florian Rivoal wrote: > > What's the criteria? > > I think specs that are reasonably stable and at least have significant > implementation progress on the path towards being able to exit CR. > > > We should at least have all RECs which means this (same as last time): > > css21 > > css3-color > > css3-namespace > > css-style-attr > > css3-selectors > > css3-mediaqueries > > Agreed. Agree. > > > Then, while they are not REC, I think the following specs should be there as > well. They're not finished, but they're important and decently stable > (although for some, TR is badly out of date and should be updated): > > > > css3-animations > > css3-background > > css3-break > > css-cascade-3 > > css-conditional > > css-counter-styles-3 > > css-flexbox-1 > > css-fonts-3 > > css3-images > > css3-multicol > > css3-speech > > css-text-decor-3 > > css3-transforms > > css3-transitions > > css-values > > Mostly agreed, but I think I would exclude css-break (unless the break- > before and break-after properties have wider implementation than I'm > aware of), and maybe css-speech (not sure what the implementation status > is there). I actually have some minor issues with this list. There are only a few I would remove due to implementations not being interoperable or no real implementations yet. Here is my list of what should be in: css3-animations css3-background css-cascade-3 css-conditional css-flexbox-1 css-fonts-3 css3-images css3-multicol css3-transforms css3-transitions css-values Here are ones I removed and why: css3-break There are still no implementations for many of the concepts in this spec. I think we should not include this yet. css-counter-styles-3 Are there 2 interoperable implementations? I am not seeing that right now. Let's shoot for 2016 snapshot. css3-speech I just don't think we have the interop here. I think we still have a long way to go to make this ready. css-text-decor-3 I just don't think the interop is there. I think this should wait. > > > Maybe these too: > > css3-page > > css-text-3 > > css3-ui > > css-variables-1 > > css-writing-modes-3 > > I would probably be inclined to include all except for css3-page, although I > don't feel strongly about any of them. > I think only css-text-3 is really ready though the others are close. I just not convinced there are any interoperable implementations of those specs to confirm that they are really ready for web authors to use. I think we should hold off on these at this time. > I think I would also suggest: > css-syntax > css-will-change > The css3-syntax maybe but I don't think css-will-change should be included yet. I know we will go round and round arguing the list for weeks. I think we should just settle on the minimum we all can agree on and then really focus on the remainder for the next year. The snapshot (if we do it right) should only be there for a year and then we will have another one. So my complete list: REC: css21 css3-color css3-namespace css-style-attr css3-selectors css3-mediaqueries Stable/or 95% interoperable: css3-animations css3-background css-cascade-3 css-conditional css-flexbox-1 css-fonts-3 css3-images css3-multicol css3-transforms css3-transitions css-values css-text-3 css3-syntax This list is already a great improvement from what we had before. Let get the 2015 snapshot out and move on to getting things done for the next snapshot in 2016. -- Thanks, Arron Eicholz
Received on Monday, 9 February 2015 16:40:07 UTC