Re: Is calc really at-risk

Hello Karen,

Friday, October 17, 2014, 12:30:28 PM, you wrote:

> I'm wondering aloud: If calc is indeed no longer at-risk, is it
> possible to remove it from the list of at-risk features here?

Wide support means that interoperability is proved by passing all the
tests, not that we guess that maybe it is fully implemented.

Marking something as at-risk has a positive benefit: it alerts
browser developers to step up their game and make sure it is well

> Karen

> On Fri, Oct 17, 2014 at 3:36 PM, Dirk Schulze <> wrote:

>  On Oct 16, 2014, at 12:34 PM, Karen Menezes <> wrote:
 >> Hey...
 >> Wanted to inquire about calc being mentioned as an at-risk feature here:
 >> It has wide support in all modern browsers and is often invaluable for layouts that mix fixed and fluid percentages (where border-box sizing doesn't help).... wrote an article here for the same:
 >> I pinged Lea Verou on her blog and her reply is below:
 >> "I doubt calc() is really at-risk, it's probably just forgotten there. at-risk means we don't have 2 independent implementations, but for calc() we do: In fact, every modern browser supports it. If you're worried, send a message to www-style and ask why it's at-risk. Probably someone will reply that it's a mistake.”
>  At risk just means that it can get removed if there is no wide
> support before going to PR and recommendation. If there are two
> independent, interoperable implementations the feature stays in the spec.
>  Greetings,
>  Dirk

 >> Would be glad to know more..
 >> Thanks for your time :)
 >> Regards,
 >> Karen

Best regards,
 Chris Lilley, Technical Director, W3C Interaction Domain

Received on Friday, 17 October 2014 11:32:19 UTC