- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Sep 2016 05:15:13 +0000
- To: public-css-archive@w3.org
> I'd prefer to at least mark it as at risk, as Chrome does not intend to implement it at this time. I don't mind doing so, but I don't see the benefit. At risk doesn't mean "not sure this is a good idea", it means "might drop if we don't have sufficient implementations to move along TR". We do have two implementations. Even if one isn't particularly relevant in terms of market share or market traction, it is as far as I know valid for demonstrating implementabilty. Ironically, process wise, I believe we would need to take the draft out of CR and to CR again to add the "at risk" mark, which would cause more delays than doing nothing. I don't mind adding "at risk" (since I don't think it makes a difference) if we end up publishing a new CR for some other reason, but process churn just for that reason seams overkill. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/423#issuecomment-245821438 using your GitHub account
Received on Friday, 9 September 2016 05:15:23 UTC