Intent to ship: |clip-path: path()|

[Boris Chiou]

As of Firefox 71, I intend to turn |clip-path: path()| on by default on all
platforms. It has been developed behind the
"layout.css.clip-path-path.enabled" preference. Safari has shipped it
already, but Chrome doesn't support it yet. There is no blocking issue, so
we would like to turn it on.

*Bug to turn on by default*:
https://bugzilla.mozilla.org/show_bug.cgi?id=1488530

*DevTools*: We don't support DevTools for this function now.

*WPT*: The reftests were added. In the shipping bug, I also added some
tests related to parsing.


Thanks

[sime....@gmail.com]

Is this a non-standard feature? I don’t see it in the spec: https://drafts.fxtf.org/css-masking-1/#the-clip-path.

[L. David Baron]

On Saturday 2019-08-31 09:21 -0700, sime....@gmail.com wrote:
> Is this a non-standard feature? I don’t see it in the spec: https://drafts.fxtf.org/css-masking-1/#the-clip-path.

Some of the links for <basic-shape> don't seem to point to the best
targets, but it's defined in:

https://drafts.csswg.org/css-shapes-2/#supported-basic-shapes

which is currently a delta on top of:

https://drafts.csswg.org/css-shapes-1/#supported-basic-shapes

-David

--
𝄞 L. David Baron http://dbaron.org/ 𝄂
𝄢 Mozilla https://www.mozilla.org/ 𝄂
Before I built a wall I'd ask to know
What I was walling in or walling out,
And to whom I was like to give offense.
- Robert Frost, Mending Wall (1914)

[Patrick Brosset]

On Fri, Aug 30, 2019 at 7:45 PM Boris Chiou <bch...@mozilla.com> wrote:

> *DevTools*: We don't support DevTools for this function now.
>

For reference: this was already discussed at Mozilla between the layout and
devtools team and agreed that we would not make a tool for this just yet
(we do have a tool for editing circle() ellipse() polygon()).
Doing a tool for this would require pretty much making a full SVG editor.

[Boris Chiou]

Thanks, everybody. I just filed a spec issue about the problem of the link
of `<basic-shape>` for clip-path [1], and another spec issue for more input
about shipping this feature from CSSWG [2].

[1] https://github.com/w3c/csswg-drafts/issues/4270
[2] https://github.com/w3c/csswg-drafts/issues/4271