- From: Karen Menezes <karen.menezes@gmail.com>
- Date: Fri, 17 Oct 2014 16:00:28 +0530
- To: Dirk Schulze <dschulze@adobe.com>
- Cc: "www-style@w3.org" <www-style@w3.org>
- Message-ID: <CAFQ+CRfEFn-hSomghsTQqncjzgvLnLN03sLt7k1AE1Nu7Eu8QA@mail.gmail.com>
Thanks Dirk... 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? http://www.w3.org/TR/css3-values/ Karen On Fri, Oct 17, 2014 at 3:36 PM, Dirk Schulze <dschulze@adobe.com> wrote: > > On Oct 16, 2014, at 12:34 PM, Karen Menezes <karen.menezes@gmail.com> > wrote: > > > Hey... > > Wanted to inquire about calc being mentioned as an at-risk feature here: > http://www.w3.org/TR/css3-values/ > > > > 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: > http://blog.karenmenezes.com/2013/dec/10/why-calc-risk/ > > > > 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 > >
Received on Friday, 17 October 2014 10:30:56 UTC