(In reply to Hamish Willee from comment #5) > > From version 91 it can be used on the <code>d</code> SVG presentation attribute. For earlier versions it is only supported on the <code>clip-path</code> and <code>offset-path</code> properties. > > Is the second statement true? i.e. is this this implementation partial, and is that a correct representation of where you can use it on FF98? Yes. Yes. The 2nd statement is true because `d` property support `path()` as well (i.e. the same syntax as offset-path). Note: the syntax of `path()` is a little bit different between `offset-path`[1] and `clip-path`[2]. [1] `path( <string> ) `, from https://drafts.fxtf.org/motion-1/#funcdef-offsetpath-pathfunc-path [2] `path( [<'fill-rule'>,]? <string> ) `, from https://drafts.csswg.org/css-shapes-1/#funcdef-path FF98 ships CSS d property, and we accept `path()` function but not path `<string>`, which matches the behavior in Chrome. There is a spec issue talking about the possible acceptable strings for CSS d property: https://github.com/w3c/svgwg/pull/374. IIRC, Eric would like to let `d` property accepts only `path()` or `none`, but other spec editors would like to support SVG path <string> as well (for backward compatibility). The current SVG2 spec only defines `<string>`. Appearally, it's a spec issue. If we would like to follow other spec editors' ideas, we should also support SVG path string CSS d property. So I think this is "partial" implementation. We can remove partial once the spec becomes clearer.
Bug 1744599 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Hamish Willee from comment #5) > > From version 91 it can be used on the <code>d</code> SVG presentation attribute. For earlier versions it is only supported on the <code>clip-path</code> and <code>offset-path</code> properties. > > Is the second statement true? i.e. is this this implementation partial, and is that a correct representation of where you can use it on FF98? Yes. Yes. The 2nd statement is true because `d` property support `path()` as well (i.e. the same syntax as offset-path). Note: the syntax of `path()` is a little bit different between `offset-path`[1] and `clip-path`[2]. [1] `path( <string> ) `, from https://drafts.fxtf.org/motion-1/#funcdef-offsetpath-pathfunc-path [2] `path( [<'fill-rule'>,]? <string> ) `, from https://drafts.csswg.org/css-shapes-1/#funcdef-path FF98 ships CSS d property, and we accept `path()` function but not path `<string>`, which matches the behavior in Chrome. There is a spec issue talking about the possible acceptable strings for CSS d property: https://github.com/w3c/svgwg/pull/374. IIRC, Eric would like to let `d` property accepts only `path()` or `none`, but other spec editors would like to support SVG path <string> as well (for backward compatibility). The current SVG2 spec only defines `<string>`. Appearally, it's a spec issue. If we would like to follow other spec editors' ideas, we should also support SVG path string CSS d property. So I think this is "partial" implementation. We can remove partial once the spec becomes clearer. (If the meaning of "partial" matches what I'm thinking. :))