Re: [svgwg] Add a way to create conic gradients (#785)
[svgwg] Issue: Add a way to create conic gradients (#785) marked as SVG21
Re: [svgwg] Is the `path()` function allowed for the `d` property? (#939)
Re: [svgwg] Support pathLength via CSS (#773)
Closed: [svg-aam] Manual publication of SVG-AAM Working Draft (#41)
[svg-aam] Update Core AAM references for 1.2 (#43)
Re: [svgwg] CSS Gradients (#1021)
[svgwg] Issue: Compatibility of focusability with HTML & platform conventions (#736) marked as Agenda+
Re: [svgwg] Compatibility of focusability with HTML & platform conventions (#736)
[svgwg] Issue: Does the entire path need to be valid in order to use a path attribute on a textPath (#393) marked as Agenda+
[svgwg] Issue: Remove stroke-linejoin 'miter-clip' or 'arcs' #592 (#1065) marked as Agenda+
[svgwg] Remove stroke-linejoin 'miter-clip' or 'arcs' #592 (#1065)
Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
[svgwg] WPT tests failing everywhere (#1064)
[svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063)
- Re: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063)
- Re: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063)
- Re: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063)
- Closed: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063)
- Re: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063)
[svgwg] Pull Request: Clarify path d animation mismatch handling for from/by and additive animations
[svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42)
- Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42)
- Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42)
- Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42)
- Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42)
- Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42)
- Closed: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42)
[svgwg] Issue: Editorial: Replacing draft URI from svgwg.org/svg2-draft to w3c.github.io/svgwg/svg2-draft/ (#1060) marked as Agenda+
[svgwg] Issue: Proposal to remove WPT tests about meshgradient meshrow meshpatch (#1061) marked as Agenda+
[svgwg] Proposal to remove WPT tests about meshgradient meshrow meshpatch (#1061)
- Re: [svgwg] Proposal to remove WPT tests about meshgradient meshrow meshpatch (#1061)
- Closed: [svgwg] Proposal to remove WPT tests about meshgradient meshrow meshpatch (#1061)
[svgwg] Editorial: Replacing draft URI from svgwg.org/svg2-draft to w3c.github.io/svgwg/svg2-draft/ (#1060)
[svgwg] Pull Request: Clarify that CSS width/height properties only apply to outer svg elements
Closed: [svgwg] SVGAnimatedLength initial value for `fx` and `fy` (#1054)
Re: [svgwg] yMid rather than YMid (#972)
Closed: [svgwg] yMid rather than YMid (#972)
Re: [svg-aam] Manual publication of SVG-AAM Working Draft (#41)
- Re: [svg-aam] Manual publication of SVG-AAM Working Draft (#41)
- Re: [svg-aam] Manual publication of SVG-AAM Working Draft (#41)
[svgwg] Pull Request: FIX #1054 Change the behavior of fx fy to be 50% as initial when not specified.
[svgwg] Merged Pull Request: [Editorial] fix typos in section 8.2
[svgwg] Issue: Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) marked as Agenda+
[svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)
- Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057)