- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 15 Oct 2014 12:42:10 -0700
- To: Dirk Schulze <dschulze@adobe.com>
- Cc: "<www-style@w3.org>" <www-style@w3.org>
On Wed, Oct 15, 2014 at 12:15 PM, Dirk Schulze <dschulze@adobe.com> wrote: > Hi, > > The CSS Shapes specification defines parts of the serialization process for basic shapes[1]. It relies on the grammar of other specifications for <border-radius> and <position>. My question is about inset() and <shape-arg>{1,4}. > > The spec says “omitting components when possible without changing the meaning”. > > Following example: > > inset(0px 0%) > > The meaning in this case would be the same if you leave out the percentage value. However, Chrome and WebKit still preserve the percentage value. I am working on a implementation of basic shapes for Gecko and currently it preserves the percentage value as well. I think it is reasonable because percentage can mean something different if there is a different context (in some cases like CSS Transforms and SVG). However, I would say that the implementations do not follow the wording then. I'm not completely sure what you're asking. Are you asking if your FF impl should omit the % there, or are you asking for the spec to change to allow keeping the 0% in the serialization? ~TJ
Received on Wednesday, 15 October 2014 19:42:58 UTC