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

2019-09-03 Thread Boris Chiou
Thanks, everybody. I just filed a spec issue about the problem of the link of `` 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 On Mon,

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

2019-09-02 Thread Patrick Brosset
On Fri, Aug 30, 2019 at 7:45 PM Boris Chiou 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

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

2019-08-31 Thread L. David Baron
On Saturday 2019-08-31 09:21 -0700, sime.vi...@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 don't seem to point to the best targets, but it's defined in:

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

2019-08-31 Thread sime . vidas
Is this a non-standard feature? I don’t see it in the spec: https://drafts.fxtf.org/css-masking-1/#the-clip-path. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

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

2019-08-30 Thread 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.