[svgwg] Support ES6 script modules in SVG (#1033)
[svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
- Re: [svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
- Re: [svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
- Re: [svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
- Re: [svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
- Re: [svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
- Re: [svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
- Re: [svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
- Re: [svgwg] Camel-cased viewBox on SVG in HTML document matched case sensitively [Deviation from Specification] (#1032)
[svgwg] Issue: Clarify whether `var()` (custom properties) are allowed in SVG presentation attributes, and how they are parsed/resolved (#1031) marked as Agenda+
[svgwg] Clarify whether `var()` (custom properties) are allowed in SVG presentation attributes, and how they are parsed/resolved (#1031)
- Re: [svgwg] Clarify whether `var()` (custom properties) are allowed in SVG presentation attributes, and how they are parsed/resolved (#1031)
- Re: [svgwg] Clarify whether `var()` (custom properties) are allowed in SVG presentation attributes, and how they are parsed/resolved (#1031)
- Re: [svgwg] Clarify whether `var()` (custom properties) are allowed in SVG presentation attributes, and how they are parsed/resolved (#1031)
Re: [svgwg] <svg:use> shadow tree shouldn't be open. (#875)
- Re: [svgwg] <svg:use> shadow tree shouldn't be open. (#875)
- Re: [svgwg] <svg:use> shadow tree shouldn't be open. (#875)
- Re: [svgwg] <svg:use> shadow tree shouldn't be open. (#875)
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)
[svgwg] Issue: <svg:use> shadow tree shouldn't be open. (#875) marked as Agenda+
[svgwg] Issue: Clarify <iframe> behavior in <svg:use> (#876) marked as Agenda+
[svgwg] Style inheritance for <use> element referencing external SVG (#1030)
- Re: [svgwg] Style inheritance for <use> element referencing external SVG (#1030)
- Re: [svgwg] Style inheritance for <use> element referencing external SVG (#1030)
- Re: [svgwg] Style inheritance for <use> element referencing external SVG (#1030)
- Re: [svgwg] Style inheritance for <use> element referencing external SVG (#1030)
[svgwg] Issue: Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029) marked as Agenda+
[svgwg] Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029)
- Re: [svgwg] Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029)
- Re: [svgwg] Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029)
- Re: [svgwg] Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029)
- Re: [svgwg] Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029)
- Re: [svgwg] Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029)
- Re: [svgwg] Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029)
- Re: [svgwg] Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element (#1029)