Hi, I’d like to unprefix the -webkit-clip-path implementation. The spec for clip-path is CSS Masking ED: https://drafts.fxtf.org/css-masking-1/ CR: https://www.w3.org/TR/css-masking-1/ Currently, WebKit has 2 independent(!) implementations: 1. The SVG clip-path CSS property that only applies to SVG elements and only allows referencing of clipPath SVG elements. 2. The -webkit-clip-path CSS property that started with basic shapes (CSS shape functions) and added support for referencing of clipPath SVG elements. While initially it just worked on HTML elements it covers SVG elements as well now. Therefore, the -webkit-clip-path implementation is a superset of the clip-path implementation and I intend to replace the latter with the former entirely. -webkit-clip-path will get an alias for clip-path. “Unprefixing" clip-path (ship with newly supported features) has been in discussion at Mozilla as well: https://groups.google.com/forum/#!searchin/mozilla.dev.platform/clip-path%7Csort:date/mozilla.dev.platform/X29xtxQRPJc/4k1avpSxDQAJ<https://groups.google.com/forum/#!searchin/mozilla.dev.platform/clip-path|sort:date/mozilla.dev.platform/X29xtxQRPJc/4k1avpSxDQAJ> https://groups.google.com/forum/#!msg/mozilla.dev.platform/RM5O36MZ4x4/mU0cO... Main concern was the confusion around the path() CSS shape function which was the only CSS shape function not defined in CSS Shapes Level 1 (but defined in the Motion spec). As a result, the CSS WG moved the function to CSS Shapes Level 1 which should address the concerns of the Mozilla community. The work happens here: https://bugs.webkit.org/show_bug.cgi?id=187888 There are a few low-priority issues left (see master bug https://bugs.webkit.org/show_bug.cgi?id=126207). They should not have a real-world affect though as they are corner cases. Please raise your concerns here on the mailing list or send your support. Thanks a lot, Dirk Schulze