W3C home > Mailing lists > Public > www-style@w3.org > December 2013

Re: [css-masking] editorial changes - spec update

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 16 Dec 2013 14:57:20 -0800
Message-ID: <52AF8550.30103@inkedblade.net>
To: www-style@w3.org
On 12/12/2013 08:02 AM, Dirk Schulze wrote:
> Hi,
> I changed the specification text and think that the following suggestions were incorporated and the open issues can be closed now.
> On Dec 11, 2013, at 11:46 AM, fantasai <fantasai.lists@inkedblade.net> wrote:
>>    1. I'd like to see mask-type and the <mask> element given their
>>       own top-level section. They're defining a mask source, not
>>       a mask application, as the rest of the properties are.
> I made mask-type and <mask> top-level sections.
> Issue 10 [1]
>>    2. Similarly, I'd like to see <clipPath> and 'clip-rule', which
>>       (afaict) define a clip "source" given a separate top-level
>>       section from 'clip' and 'clip-path', which define a clip path's
>>       application.
> I made <clipPath> and ‘clip-rule’ top-level sections.

If I understand correctly, 'clip-rule' only applies within <clipPath>,
and 'mask-type' only applies to <mask>. So these things should be
grouped together, to help convey this very tight association.

I can see two ways of doing this:

1. Give <mask> and <clipPath> individual sections, e.g.

      [properties that apply clipping]
   SVG Clip Path Sources
      Defining a clipping path: the <clipPath> element
      Filling the clipping path: the clip-rule property
   Layered Masks
      [properties that apply layered masks]
   SVG Mask Sources
      Defining a mask source: the <mask> element
      Specifying mask interpretation: the mask-type property
   Box Masks

2. Put <mask> and <clipPath> both into an SVG section

      [properties that apply clipping]
   SVG Mask and Clip Path Sources
      Defining a clipping path: the <clipPath> element
      Filling the clipping path: the clip-rule property
      Defining a mask source: the <mask> element
      Specifying mask interpretation: the mask-type property
   Layered Masks
      [properties that apply layered masks]
   Box Masks
      Defining mask interpretation: the mask-type property

>>    4. Layered Masks needs a new name, since at the moment we only
>>       have one layer. :)
> As discussed earlier in this thread, it is the intention of the editors
> to make mask a layered model. In the current version just one layer is
> supported. A note in the spec makes clear that this will change with
> the next level.

Yes, but I think it's a little weird to have a title that doesn't
reflect what it's currently titling.

How about "Positioned Masks"? It's accurate now as well as in the
future, and reflects a fundamental difference between this type
of mask and the box-image type of mask. Also, even once we have
layers, the positioning features are still going to be more
important than the layering in actual usage.

>>    7. The terms local coordinate system, user coordinate system, and
>>       object bounding box units are only used in the definition of
>>       <mask>. They should be relegated to that section (or merely
>>       referenced from SVG), not defined up front. The top terminology
>>       section should be for definitions and concepts used throughout
>>       the spec, that someone would need to know to understand random
>>       sections they jump to once through the introductory sections.
> Local coordinate system was indeed not used in this spec. I used the
> SVG for most other terms mainly used by SVG. I kept the definition
> for "user coordinate system” since the definition of SVG 1.1 is
> extended. It is clarified how “user coordinate system” works on the
> CSS boxing model.

It's fine to keep it if you need it, but since it's really very specific
to the SVG bits, maybe it would be better to move the definition closer
to where it's used? It's not a concept that a CSS-only user would need
to understand, and it's a rather long and involved definition, so I'm
afraid that that it's more confusing than helpful to have it up front.

(I try to keep Terminology sections at the top focused on globally-used
concepts, where not understanding the terms would impede understanding
of a substantial portion of the spec. Other terms I define more locally.)

> Issue 18 [9]
> Still under discussion: issue 19 [10] status: open
>>   10. # The usage of mask-box-image corresponds to the border-image property
>>       # of CSS Background and Borders [CSS3BG].
>>       Except that the image is used as a mask rather than rendered on
>>       top of the background, right? :) You should say that up front.
> I clarified that the image is sliced and scaled and the properties
> behave similar like border-image*, but that the image is used as a mask.

s/usage/syntax/ and I'll consider this closed. :)

> With your permission, fantasai, I would like to close the issues (not
> marked as open above) as resolved.
> [1] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-10
> [2] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-11

Keep these open for the moment.

> [3] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-12

I'm OK to close this.

> [4] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-13

See above. I think we do need a better name for this section. :)

> [5] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-14

OK to close

> [7] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-16

See above.

> [9] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-18

OK to close

> [11] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-20

OK to close given s/usage/syntax/

> [12] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-21
> [13] http://dev.w3.org/fxtf/masking/issues-lc-2013.html#issue-22

OK to close

Please add another editorial issue:
   - Section titles should explain the purpose of each property,
     as in http://dev.w3.org/csswg/css-backgrounds/
Should be easy to fix, and I think would help people find what
they're looking for if they don't already know what it's called.

Received on Tuesday, 17 December 2013 00:18:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:38 UTC