public-svg-issues@w3.org from February 2026 by author

Ahmad Saleem via GitHub

• Re: [svgwg] Compatibility of focusability with HTML & platform conventions (#736) (Tuesday, 10 February)
• Re: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063) (Tuesday, 10 February)
• Re: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063) (Tuesday, 10 February)
• [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063) (Tuesday, 10 February)

caribouW3 via GitHub

• Re: [svgwg] yMid rather than YMid (#972) (Wednesday, 4 February)
• Closed: [svgwg] yMid rather than YMid (#972) (Wednesday, 4 February)

Cynthia Shelly via GitHub

• Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42) (Thursday, 12 February)

Daniel Montalvo via GitHub

• Re: [svg-aam] Manual publication of SVG-AAM Working Draft (#41) (Thursday, 12 February)
• Closed: [svg-aam] Manual publication of SVG-AAM Working Draft (#41) (Thursday, 12 February)
• Closed: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42) (Thursday, 12 February)
• [svg-aam] Update Core AAM references for 1.2 (#43) (Wednesday, 11 February)
• Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42) (Tuesday, 10 February)
• Re: [svg-aam] Manual publication of SVG-AAM Working Draft (#41) (Tuesday, 10 February)
• Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42) (Monday, 9 February)
• [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42) (Monday, 9 February)

Divyansh Mangal via GitHub

• Re: [svgwg] Clarify that CSS width/height properties only apply to outer svg elements (#1059) (Monday, 9 February)
• [svgwg] Pull Request: Clarify that CSS width/height properties only apply to outer svg elements (Sunday, 8 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• [svgwg] Issue: Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) marked as Agenda+ (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)

Karl Dubost via GitHub

• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393) (Saturday, 14 February)
• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393) (Friday, 13 February)
• Re: [svgwg] Add a way to create conic gradients (#785) (Friday, 13 February)
• [svgwg] Issue: Add a way to create conic gradients (#785) marked as SVG21 (Friday, 13 February)
• Re: [svgwg] CSS Gradients (#1021) (Friday, 13 February)
• Closed: [svgwg] Proposal to remove WPT tests about meshgradient meshrow meshpatch (#1061) (Friday, 13 February)
• Re: [svgwg] Proposal to remove WPT tests about meshgradient meshrow meshpatch (#1061) (Thursday, 12 February)
• [svgwg] Issue: Compatibility of focusability with HTML & platform conventions (#736) marked as Agenda+ (Tuesday, 10 February)
• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393) (Tuesday, 10 February)
• Re: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063) (Tuesday, 10 February)
• Closed: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063) (Tuesday, 10 February)
• [svgwg] Issue: Does the entire path need to be valid in order to use a path attribute on a textPath (#393) marked as Agenda+ (Tuesday, 10 February)
• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393) (Tuesday, 10 February)
• [svgwg] Issue: Remove stroke-linejoin 'miter-clip' or 'arcs' #592 (#1065) marked as Agenda+ (Tuesday, 10 February)
• Re: [svgwg] Remove stroke-linejoin 'miter-clip' or 'arcs' #592 (#1065) (Tuesday, 10 February)
• [svgwg] Remove stroke-linejoin 'miter-clip' or 'arcs' #592 (#1065) (Tuesday, 10 February)
• [svgwg] WPT tests failing everywhere (#1064) (Tuesday, 10 February)
• Re: [svgwg] <hatch> test coverage on WPT or support in SVGWG? (#1063) (Tuesday, 10 February)
• [svgwg] Issue: Editorial: Replacing draft URI from svgwg.org/svg2-draft to w3c.github.io/svgwg/svg2-draft/ (#1060) marked as Agenda+ (Monday, 9 February)
• [svgwg] Issue: Proposal to remove WPT tests about meshgradient meshrow meshpatch (#1061) marked as Agenda+ (Monday, 9 February)
• [svgwg] Proposal to remove WPT tests about meshgradient meshrow meshpatch (#1061) (Monday, 9 February)
• [svgwg] Editorial: Replacing draft URI from svgwg.org/svg2-draft to w3c.github.io/svgwg/svg2-draft/ (#1060) (Monday, 9 February)
• Re: [svgwg] SVG path animation: unclear behavior for from + by when commands mismatch (#1056) (Thursday, 5 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Thursday, 5 February)
• Closed: [svgwg] SVGAnimatedLength initial value for `fx` and `fy` (#1054) (Wednesday, 4 February)
• [svgwg] Merged Pull Request: FIX #1054 Change the behavior of fx fy to be 50% as initial when not specified. (Wednesday, 4 February)
• [svgwg] Pull Request: FIX #1054 Change the behavior of fx fy to be 50% as initial when not specified. (Wednesday, 4 February)
• [svgwg] Merged Pull Request: [Editorial] fix typos in section 8.2 (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] Should `width` and `height` apply to nested `svg` elements as CSS properties (#1057) (Wednesday, 4 February)
• Re: [svgwg] `SVGTransform.matrix` returns `SVGMatrix` in all browsers (#1055) (Tuesday, 3 February)
• [svgwg] Issue: `SVGTransform.matrix` returns `SVGMatrix` in all browsers (#1055) marked as Agenda+ (Tuesday, 3 February)

Mark Rogers via GitHub

• Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42) (Tuesday, 10 February)
• Re: [svg-aam] Take a pass at existing pointers to the SVG AAM and CORE AAM sspecifications (#42) (Monday, 9 February)
• Re: [svg-aam] Manual publication of SVG-AAM Working Draft (#41) (Wednesday, 4 February)

viralipurbey via GitHub

• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393) (Friday, 13 February)
• [svgwg] Pull Request: Clarify path d animation mismatch handling for from/by and additive animations (Monday, 9 February)
• [svgwg] Issue: SVG path animation: unclear behavior for from + by when commands mismatch (#1056) marked as Agenda+ (Tuesday, 3 February)
• [svgwg] SVG path animation: unclear behavior for from + by when commands mismatch (#1056) (Tuesday, 3 February)

一丝 via GitHub

• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393) (Friday, 13 February)
• Re: [svgwg] Is the `path()` function allowed for the `d` property? (#939) (Friday, 13 February)
• Re: [svgwg] Support pathLength via CSS (#773) (Friday, 13 February)
• Re: [svgwg] CSS Gradients (#1021) (Tuesday, 10 February)
• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393) (Tuesday, 10 February)
• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393) (Tuesday, 10 February)

Last message date: Saturday, 14 February 2026 12:08:04 UTC