public-svg-issues@w3.org from December 2022 by thread

[svgwg] Merged Pull Request: Stop using the DocumentAndElementEventHandlers interface mixin caribouW3 via GitHub (Wednesday, 21 December)

Re: [svgwg] Stop using the DocumentAndElementEventHandlers interface mixin (#895) Philip Jägenstedt via GitHub (Wednesday, 21 December)

Closed: [svgwg] Referencing SVGs through USE from other domains (#707) Alex Inkin via GitHub (Sunday, 18 December)

Re: [svgwg] Referencing SVGs through USE from other domains (#707) Jun via GitHub (Friday, 16 December)

[svgwg] Pull Request: Svg next hackermondal via GitHub (Tuesday, 13 December)

[svgwg] Pull Request: Remove support for data: URL in SVGUseElement Jun via GitHub (Friday, 9 December)

Re: [svg-aam] When is the "symbol" element mappable? (#17) Brennan Young via GitHub (Thursday, 8 December)

Re: [svg-aam] Should the mappings of a nested 'svg' be different from that of a root 'svg'? (#18) Brennan Young via GitHub (Thursday, 8 December)

[svg-aam] Browsers off spec? SVG maps to "group" but the spec suggests it should map to "graphics-document" (#22) Brennan Young via GitHub (Thursday, 8 December)

Re: [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec (#309) Robert Longson via GitHub (Tuesday, 6 December)

Closed: [svgwg] Is "M0,0L100,0ZL100,50L200,200ZL,0,200Z" 1 subpath or 3? (#866) tatarize via GitHub (Monday, 5 December)

Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers (#266) b-hayes via GitHub (Monday, 5 December)

Last message date: Thursday, 22 December 2022 09:31:15 UTC