- From: Dirk Schulze <dschulze@adobe.com>
- Date: Sat, 12 Apr 2014 06:05:35 +0000
- To: fantasai <fantasai.lists@inkedblade.net>
- CC: "www-style@w3.org" <www-style@w3.org>
Hi fantasai, On Dec 17, 2013, at 12:30 AM, fantasai <fantasai.lists@inkedblade.net> wrote: > On 12/13/2013 11:27 AM, Dirk Schulze wrote: >> >> On Dec 13, 2013, at 8:09 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> >>> On Wed, Dec 11, 2013 at 7:54 AM, Dirk Schulze <dschulze@adobe.com> wrote: >>>> Hi, >>>> >>>> On Dec 11, 2013, at 11:46 AM, fantasai <fantasai.lists@inkedblade.net> wrote: >>>> >>>>> 7. clip-rule is not defined. At all. There's some syntax, an explanation >>>>> of how the two values differ, and an example, but no definition >>>>> of what the property actually *does*. >>>> >>>> I put the explanation into the example [1]. Examples are normative. >>> >>> Examples are informative. >> >> Thanks for the clarification. >> >> The definition of clip-rule is still complete. fill-rule is normatively >> referenced. It is said that UAs must follow what fill-rule does and there >> is a normative paragraph that clip-rule just applies to descendants of >> the <clipPath> element. > > I can infer that 'evenodd' and 'nonzero' on 'clip-rule' are interpreted > analogously to 'fill-rule', but nothing says how it is interpreted for > clipping. Nothing says that it applies to the clipping path, for example, > as opposed to some other polygon. > > You need a real definition here. I added normative tests describing what even odd and nonzero aim to do and explained that this is effecting the shape use in the clipping region [1]. The actual algorithm is referenced from SVG 1.1. Please tell me if you still believe that this is not sufficient enough.[2] Greetings, Dirk [1] http://dev.w3.org/fxtf/css-masking-1/#the-clip-rule [2] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-8 > > ~fantasai >
Received on Saturday, 12 April 2014 06:06:05 UTC