Friday, 27 March 2026
- [svg-aam] Implementation role mapping for SVG elements (#52)
- Re: [svg-aam] SVG-AAM should address which elements should map to ARIA `generic` role (#21)
Thursday, 26 March 2026
- Re: [svgwg] Testing HTML/CSS <-> SVG interoperability (#1015)
- Re: [svgwg] Multi-Page support (#157)
- Re: [svgwg] New Interface SVGPathSegment: segments should be more editable (#974)
- Re: [svgwg] `SVGPathSegment` should be a dictionary, not a `[NoInterfaceObject]` interface (#1082)
- Re: [svgwg] Publish current status of SVG (#938)
- Re: [svgwg] Multi-Page support (#157)
- Re: [svgwg] Support pathLength via CSS (#773)
- [svgwg] Issue: `SVGPathSegment` should be a dictionary, not a `[NoInterfaceObject]` interface (#1082) marked as Agenda+
- [svgwg] `SVGPathSegment` should be a dictionary, not a `[NoInterfaceObject]` interface (#1082)
- Re: [svgwg] New Interface SVGPathSegment: segments should be more editable (#974)
- [svgwg] Issue: New Interface SVGPathSegment: segments should be more editable (#974) marked as Agenda+
Wednesday, 25 March 2026
Tuesday, 24 March 2026
Saturday, 21 March 2026
Friday, 20 March 2026
- [svgwg] What are the allowed values for stop-color ? (#1080)
- [svgwg] Issue: Publish current status of SVG (#938) marked as Agenda+
- Closed: [svg-aam] Graphics AAM links broken (#48)
- [svg-aam] Kicking off SVG-AAM work (#51)
- [svg-aam] svg-aam: remove mappings for SVG elements removed between SVG2 2016 CR and SVG2 2018 CR (#50)
Thursday, 19 March 2026
- Re: [svgwg] `baseline-y` in SVG (#1075)
- Re: [svg-aam] What does 'valid' mean in 'link role if the element has a valid href or xlink:href attribute' (#47)
- Re: [svgwg] Update from api.csswg.org/bikeshed to spec-generator (#1079)
- [svgwg] Pull Request: Update from api.csswg.org/bikeshed to spec-generator
- Re: [svg-aam] Some links go to the wrong place (#49)
- Re: [svg-aam] What does 'valid' mean in 'link role if the element has a valid href or xlink:href attribute' (#47)
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
- Re: [svgwg] `baseline-y` in SVG (#1075)
- Re: [svgwg] Should getBBox returns values when the shape can't be drawn (#1018)
- Re: [svgwg] FIX #1018 getbbox returns 0,0,0,0 when values are invalid or absent. (#1078)
- Re: [svgwg] Remove SVGElementInstance (correspondingElement / correspondingUseElement) (#1070)
- Re: [svgwg] Overflow property behavior / spec on SVG element doesn't match reality. (#1072)
- Re: [svgwg] Overflow property behavior / spec on SVG element doesn't match reality. (#1072)
- [svgwg] Pull Request: FIX #1018 getbbox returns 0,0,0,0 when values are invalid or absent.
- Re: [svgwg] Should getBBox returns values when the shape can't be drawn (#1018)
- Re: [svgwg] Should getBBox returns values when the shape can't be drawn (#1018)
- Re: [svgwg] Should getBBox returns values when the shape can't be drawn (#1018)
- Re: [svgwg] Should getBBox returns values when the shape can't be drawn (#1018)
- [svgwg] Pull Request: Update <textPath> `path`/`href` fallback behavior per WG resolution
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
Wednesday, 18 March 2026
- Re: [svgwg] `baseline-y` in SVG (#1075)
- Re: [svgwg] `baseline-y` in SVG (#1075)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
- Re: [svgwg] Clarify <iframe> behavior in <svg:use> (#876)
- Re: [svgwg] Should getBBox returns values when the shape can't be drawn (#1018)
- [svg-aam] Some links go to the wrong place (#49)
- Re: [svgwg] Building a schema for SVG / Creating an SVG profile for IEC 61850-6-2 (#699)
- [svgwg] Issue: Building a schema for SVG / Creating an SVG profile for IEC 61850-6-2 (#699) marked as Agenda+
- Re: [svgwg] Multi-Page support (#157)
- [svgwg] Issue: Multi-Page support (#157) marked as Agenda+
- Re: [svg-aam] What does 'valid' mean in 'link role if the element has a valid href or xlink:href attribute' (#47)
- Re: [svgwg] Fix TOC styling in Editor's Drafts for specs on svgwg.org (#194)
- Closed: [svgwg] Fix TOC styling in Editor's Drafts for specs on svgwg.org (#194)
- Re: [svgwg] Remove or add warnings to outdated draft specs on dev.w3.org (#188)
- Closed: [svgwg] Remove or add warnings to outdated draft specs on dev.w3.org (#188)
- Re: [svgwg] Triage all issues from Tracker (#250)
- Closed: [svgwg] Triage all issues from Tracker (#250)
- Closed: [svgwg] SVGWG Agenda TPAC 2019 (#731)
- Re: [svgwg] SVGWG Agenda TPAC 2019 (#731)
- Re: [svgwg] Mixed content issue when viewing GitHub-hosted spec over HTTPS (#283)
- Closed: [svgwg] Mixed content issue when viewing GitHub-hosted spec over HTTPS (#283)
- Re: [svgwg] Corner-case incompleteness of stroke-miterlimit specification for "arcs" join (#772)
- Closed: [svgwg] Corner-case incompleteness of stroke-miterlimit specification for "arcs" join (#772)
- Re: [svgwg] Alternative arcs join fallback heuristics (SVG 2 sec 13.5.7,9) (#771)
- Closed: [svgwg] Alternative arcs join fallback heuristics (SVG 2 sec 13.5.7,9) (#771)
- Re: [svgwg] SVG 2 spec section 13.5.7 (probably) incorrect for miter-clip (and arcs?) (#745)
- Closed: [svgwg] SVG 2 spec section 13.5.7 (probably) incorrect for miter-clip (and arcs?) (#745)
- [svg-aam] Graphics AAM links broken (#48)
- Re: [svg-aam] What does 'valid' mean in 'link role if the element has a valid href or xlink:href attribute' (#47)
- Re: [svgwg] Overflow property behavior / spec on SVG element doesn't match reality. (#1072)
- [svgwg] Issue: Overflow property behavior / spec on SVG element doesn't match reality. (#1072) marked as Agenda+
- Closed: [svgwg] Remove stroke-linejoin 'miter-clip' or 'arcs' #592 (#1065)
- [svgwg] Merged Pull Request: Fix #1065 - Remove stroke-linejoin 'miter-clip' or 'arcs'
- Re: [svgwg] Fix #1065 - Remove stroke-linejoin 'miter-clip' or 'arcs' (#1074)
- [svg-aam] What does 'valid' mean in 'link role if the element has a valid href or xlink:href attribute' (#47)
- Re: [svgwg] Remove SVGElementInstance (correspondingElement / correspondingUseElement) (#1070)
- [svgwg] Pull Request: Remove SVGElementInstance mixin interface - Fix #1070
- Re: [svgwg] Remove SVGElementInstance (correspondingElement / correspondingUseElement) (#1070)
- Re: [svgwg] Remove SVGElementInstance (correspondingElement / correspondingUseElement) (#1070)
- Re: [svgwg] Remove/Better testing correspondingElement and correspondingUseElement from SVGElement (#1070)
- Re: [svgwg] Remove/Better testing correspondingElement and correspondingUseElement from SVGElement (#1070)
- Re: [svgwg] Remove/Better testing correspondingElement and correspondingUseElement from SVGElement (#1070)
- Re: [svgwg] `baseline-y` in SVG (#1075)
- [svgwg] Issue: `baseline-y` in SVG (#1075) marked as SVG21
Monday, 16 March 2026
Friday, 13 March 2026
Thursday, 12 March 2026
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] Fix #1065 - Remove stroke-linejoin 'miter-clip' or 'arcs' (#1074)
- [svgwg] Merged Pull Request: #fix 828 - Drop display properties from UA svg CSS.
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- [svgwg] Pull Request: Fix #1065 - Remove stroke-linejoin 'miter-clip' or 'arcs'
Wednesday, 11 March 2026
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] UA stylesheet seems to require title as display: none but browsers do display: inline (#828)
- Re: [svg-aam] allowed roles for a (#46)
- [svg-aam] Issue: allowed roles for a (#46) marked as question
- [svg-aam] allowed roles for a (#46)
- Re: [svgwg] UA stylesheet seems to require title as display: none but browsers do display: inline (#828)
- Re: [svgwg] Remove stroke-linejoin 'miter-clip' or 'arcs' #592 (#1065)
- Re: [svgwg] Remove shape-inside and shape-substract from SVG2 (#1067)
- [svgwg] Pull Request: Add path-length CSS property definition (Section 9.6.1)
- [svgwg] Issue: Support pathLength via CSS (#773) marked as Agenda+
Saturday, 7 March 2026
- Re: [svgwg] Overflow property behavior / spec on SVG element doesn't match reality. (#1072)
- [svgwg] Overflow property behavior / spec on SVG element doesn't match reality. (#1072)
Thursday, 5 March 2026
- Re: [svgwg] SVG path animation: unclear behavior for from + by when commands mismatch (#1056)
- Closed: [svgwg] SVG path animation: unclear behavior for from + by when commands mismatch (#1056)
- [svgwg] Pull Request: #fix 828 - Drop display properties from UA svg CSS.
- Re: [svgwg] UA stylesheet seems to require title as display: none but browsers do display: inline (#828)
- Re: [svgwg] UA stylesheet seems to require title as display: none but browsers do display: inline (#828)
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] UA stylesheet seems to require title as display: none but browsers do display: inline (#828)
- Re: [svgwg] UA stylesheet seems to require title as display: none but browsers do display: inline (#828)
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
Wednesday, 4 March 2026
- Re: [svgwg] Remove correspondingElement and correspondingUseElement from SVGElement (#1070)
- [svgwg] Issue: Remove correspondingElement and correspondingUseElement from SVGElement (#1070) marked as Agenda+
- [svgwg] Remove correspondingElement and correspondingUseElement from SVGElement (#1070)
- Re: [svgwg] WPT tests failing everywhere (#1064)
- [svgwg] Merged Pull Request: Clarify path d animation mismatch handling for from/by and additive animations
- Closed: [svgwg] CSS (#1069)
- Re: [svgwg] CSS (#1069)
- [svgwg] CSS (#1069)
Tuesday, 3 March 2026
- Re: [svgwg] UA stylesheet seems to require title as display: none but browsers do display: inline (#828)
- [svgwg] Issue: UA stylesheet seems to require title as display: none but browsers do display: inline (#828) marked as Agenda+
- [svgwg] Issue: Does the entire path need to be valid in order to use a path attribute on a textPath (#393) marked as Agenda+
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- [svgwg] Issue: SVGTextPathElement interface seems to be missing properties (#391) marked as SVG21
- [svgwg] Issue: Remove "side" attribute from "textPath" (#1068) marked as Agenda+
- [svgwg] Remove "side" attribute from "textPath" (#1068)
- Re: [svgwg] Remove shape-inside and shape-substract from SVG2 (#1067)
- [svgwg] Issue: Remove shape-inside and shape-substract from SVG2 (#1067) marked as Agenda+
- [svgwg] Remove shape-inside and shape-substract from SVG2 (#1067)
Monday, 2 March 2026
- Re: [svgwg] Clarify path d animation mismatch handling for from/by and additive animations (#1062)
- Re: [svgwg] SVG path animation: unclear behavior for from + by when commands mismatch (#1056)
- Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (#393)
- Re: [svgwg] Support pathLength via CSS (#773)