Re: Groups in clipPaths?

It was *probably* an XML DTD validation issue, that an element is only able
to constrain its immediate children and not all descendents.  If you allow
a `<g>`, then you allow anything that is a valid child of a `<g>`, which
would include things like `<image>` that don't make sense in a clipPath.

But the spec is much less tied to DTD validation these days, so that's not
a good justification anymore.  Furthermore, the clipPath can contain a
`<use>`, and the `<use>` can create a copy of an image, so the argument
fails on that point.

I'd personally prefer to handle the question on the rendering side, anyway,
allowing arbitrary containers and just skipping over any embedded content
that can't be converted to a vector outline.

Have you tested it? What do browsers currently do?  Do they ignore the
entire group or use the shapes inside it?

When you get some data, the correct place to file an issue is the FXTF
repo, https://github.com/w3c/fxtf-drafts/issues/
Be sure to start the issue subject with [css-masking].

~ABR

On 2 August 2016 at 10:26, Paul LeBeau <paul.lebeau@gmail.com> wrote:

> Hi all
>
> Just wondering if anyone can remember why groups are not allowed in
> clipPaths?
>
> Paul
>
>