W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > March 2019

Re: [fxtf-drafts] [css-masking-1] Clarify behaviour of clipPathUnits="objectBoundingBox" when placed on a child clipPath (#247)

From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
Date: Sat, 02 Mar 2019 22:51:44 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-468968143-1551567103-sysbot+gh@w3.org>
Related issue raised on Firefox because of interop failures: https://bugzilla.mozilla.org/show_bug.cgi?id=1531890

That issue is about `clip-path` property applied to a *child* of a `<clipPath>` element, and I'm confident calling that a Firefox bug — but I agree that the spec could be clarified.

For this issue (`clip-path` property on the `<clipPath>` element itself), I agree with Dirk that it is less clear what *should* happen.  Both Chromium and Firefox use the original element's user space for the secondary clipping path ([test case CodePen](https://codepen.io/AmeliaBR/collab/fd314d690be3c48a72b238d695db395e)), and that is consistent with the spec describing this structure as an intersection of the two clipping paths.  But it still needs to be made explicit.

cc @longsonr

-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/247#issuecomment-468968143 using your GitHub account
Received on Saturday, 2 March 2019 22:51:46 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 2 March 2019 22:51:46 UTC