Monday, 29 July 2019
- Re: [svgwg] How should ResizeObserver work for SVG layout elements? (#713)
- Re: [svgwg] Make "show" widget in element definitions boxes play nicely with screen readers (#714)
- Re: [svgwg] Defer onfocusin and onfocusout (#715)
- Re: [svgwg] [svg-native] Decide whether reusable graphical elements are needed (#689)
Sunday, 28 July 2019
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Clean up definitions around transforms on root SVG element (#360)
Saturday, 27 July 2019
- [svgwg] Remove outdated note on hit-testing and root element (#718)
- [svgwg] Issue: Remove outdated note on hit-testing and root element (#718) marked as CSS Consistency
- [svgwg] new commits pushed by AmeliaBR
- [svgwg] Merged Pull Request: Expanded note on server configuration and SVGZ
- Closed: [svgwg] A separate MIME type for svgz files is needed (#701)
Wednesday, 24 July 2019
Tuesday, 23 July 2019
- Re: [svgwg] Typo `referrerpolicy` content attribute type definition (#712)
- Re: [svgwg] Discard "discard" elements (#717)
- Re: [svgwg] Discard "discard" elements (#717)
- Re: [svgwg] Typo `referrerpolicy` content attribute type definition (#712)
- [svgwg] Issue: Typo `referrerpolicy` content attribute type definition (#712) marked as Needs editing
- [svgwg] Issue: Defer onfocusin and onfocusout (#715) marked as Agenda+
- Re: [svgwg] Discard "discard" elements (#717)
- [svgwg] Issue: Discard "discard" elements (#717) marked as SVG Animations
Friday, 19 July 2019
Wednesday, 17 July 2019
Tuesday, 16 July 2019
Monday, 15 July 2019
- Re: [svgwg] SVGAElement implements two conflicting interfaces (#312)
- Re: [svgwg] Referencing SVGs through USE from other domains (#707)
- Re: [svgwg] [svg-native] Decide whether reusable graphical elements are needed (#689)
- Re: [svgwg] SVGAElement implements two conflicting interfaces (#312)
- Re: [svgwg] [svg-native] Decide whether reusable graphical elements are needed (#689)
- Re: [svgwg] Referencing SVGs through USE from other domains (#707)
- Re: [svgwg] [svg-native] Decide whether reusable graphical elements are needed (#689)
- Re: [svgwg] Referencing SVGs through USE from other domains (#707)
- Re: [svgwg] Referencing SVGs through USE from other domains (#707)
- Re: [svgwg] Referencing SVGs through USE from other domains (#707)
- Re: [svgwg] SVGAElement implements two conflicting interfaces (#312)
- Re: [svgwg] xlink:href in <animate>, <use>, etc. doesn't work in sourceless iframes (#700)
- Re: [svgwg] SVGAElement implements two conflicting interfaces (#312)
- Re: [svgwg] [svg-native] Decide whether reusable graphical elements are needed (#689)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
Sunday, 14 July 2019
- Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript (#291)
- Closed: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript (#291)
- [svgwg] Pull Request: Expanded note on server configuration and SVGZ
- Re: [svgwg] Make "show" widget in element definitions boxes play nicely with screen readers (#714)
- [svgwg] Merged Pull Request: Make "show" widget in element definitions boxes play nicely with screen readers
- [svgwg] new commits pushed by AmeliaBR
- Closed: [svgwg] Make "show" widget in element definitions boxes play nicely with screen readers (#110)
- Re: [svgwg] Make "show" widget in element definitions boxes play nicely with screen readers (#714)
- [svgwg] Defer onfocusin and onfocusout (#715)
- [svgwg] Pull Request: Make "show" widget in element definitions boxes play nicely with screen readers
Friday, 12 July 2019
- Re: [svgwg] text-overflow property is missing from attribute index (#711)
- Re: [svgwg] text-overflow property is missing from attribute index (#711)
Wednesday, 10 July 2019
- [svgwg] How should ResizeObserver work for SVG layout elements? (#713)
- [svgwg] Issue: How should ResizeObserver work for SVG layout elements? (#713) marked as CSS Consistency
Tuesday, 9 July 2019
- Re: [svgwg] [svg-native] Decide whether reusable graphical elements are needed (#689)
- Re: [svgwg] [svg-native] Decide whether reusable graphical elements are needed (#689)
- Re: [svgwg] [svg-native] Decide whether reusable graphical elements are needed (#689)
Sunday, 7 July 2019
- Closed: [svgwg] text-overflow property is missing from attribute index (#711)
- Re: [svgwg] text-overflow property is missing from attribute index (#711)
- Re: [svgwg] text-overflow property is missing from attribute index (#711)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
- [svgwg] Typo `referrerPolicy` content attribute type definition (#712)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
Saturday, 6 July 2019
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
- Re: [svgwg] xlink:href in <animate> doesn't work in sourceless iframes (#700)
- [svgwg] Issue: xlink:href in <animate> doesn't work in sourceless iframes (#700) marked as HTML Consistency
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
Friday, 5 July 2019
- Re: [svgwg] text-overflow property is missing from attribute index (#711)
- [svgwg] Issue: text-overflow property is missing from attribute index (#711) marked as Text chapter
- [svgwg] text-overflow property is missing from attribute index (#711)
- Re: [svgwg] SVG no longer defines any attributes as required (#710)
- Re: [svgwg] SVG no longer defines any attributes as required (#710)
- [svgwg] Issue: SVG no longer defines any attributes as required (#710) marked as Basic shapes chapter
- Re: [svgwg] SVG no longer defines any attributes as required (#710)
- [svgwg] SVG no longer defines any attributes as required (#710)
Thursday, 4 July 2019
- Re: [svgwg] SVGAElement implements two conflicting interfaces (#312)
- [svgwg] Issue: SVGAElement implements two conflicting interfaces (#312) marked as Agenda+
- Re: [svgwg] SVGAElement implements two conflicting interfaces (#312)
- Re: [svgwg] SVGAElement has a clashing definition of href (#709)
- Closed: [svgwg] SVGAElement has a clashing definition of href (#709)
- [svgwg] SVGAElement has a clashing definition of href (#709)
Wednesday, 3 July 2019
- Re: [svgwg] Tracking issue for the renaming of HTMLOrSVGElement to something inclusive for MathML (#708)
- Re: [svgwg] Tracking issue for the renaming of HTMLOrSVGElement to something inclusive for MathML (#708)
- [svgwg] Issue: Tracking issue for the renaming of HTMLOrSVGElement to something inclusive for MathML (#708) marked as Basic Data Types and Interfaces chapter
- [svgwg] Tracking issue for the renaming of HTMLOrSVGElement to something inclusive for MathML (#708)
Tuesday, 2 July 2019
- Re: [svgwg] A separate MIME type for svgz files is needed (#701)
- Re: [svgwg] A separate MIME type for svgz files is needed (#701)
- Re: [svgwg] A separate MIME type for svgz files is needed (#701)
Monday, 1 July 2019
- Re: [svgwg] [svg-native] Which CSS concepts should be supported in presentation attributes? (#681)
- Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript (#291)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Referencing SVGs through USE from other domains (#707)
- Re: [svgwg] Referencing SVGs through USE from other domains (#707)
- [svgwg] Issue: Referencing SVGs through USE from other domains (#707) marked as Document structure chapter
- [svgwg] Referencing SVGs through USE from other domains (#707)