Friday, 28 June 2019
- Re: [svgwg] A separate MIME type for svgz files is needed (#701)
- 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] A separate MIME type for svgz files is needed (#701)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
Thursday, 27 June 2019
- Re: [svgwg] A separate MIME type for svgz files is needed (#701)
- Re: [svgwg] Internet Media type `image/svg+xml' (#685)
- [svgwg] new commits pushed by svgeesus
- [svgwg] Merged Pull Request: Added paragraph about Tiny 1.2 being deprecated (bug #199)
Tuesday, 25 June 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)
- Re: [svgwg] Clarify SVG Integration spec re expectations for SVG in OpenType (#145)
- Re: [svgwg] Clarify SVG Integration spec re expectations for SVG in OpenType (#145)
- Re: [svgwg] Clarify SVG Integration spec re expectations for SVG in OpenType (#145)
Monday, 24 June 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] Text with multiple x="" values should be shaped as if it was not broken (#631)
Sunday, 23 June 2019
Saturday, 22 June 2019
- 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)
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
Friday, 21 June 2019
- [svgwg] Issue: Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706) marked as Basic Data Types and Interfaces chapter
- Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
- [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706)
Thursday, 20 June 2019
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Closed: [svgwg] SVG2 path data coordinates are currently spec'd as integers. (#335)
- Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers. (#335)
- Re: [svgwg] grammar for "closepath can substitute for final coordinate" is broken (#325)
- Re: [svgwg] Scientific notation has been removed from the path EBNF (#286)
- Closed: [svgwg] Scientific notation has been removed from the path EBNF (#286)
- Re: [svgwg] grammar for "closepath can substitute for final coordinate" is broken (#325)
- Closed: [svgwg] grammar for "closepath can substitute for final coordinate" is broken (#325)
- Closed: [svgwg] Floating point number format discordance (SVG vs CSS vs browsers) (#331)
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Merged Pull Request: Align path number parsing with CSS Numbers. Fixes #331
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Align path number parsing with CSS Numbers. Fixes #331 (#697)
- Closed: [svgwg] All links to "default sizing algorithm" are deadlink (#702)
- [svgwg] new commits pushed by dirkschulze
- [svgwg] Merged Pull Request: Update link to default sizing algorithm. Fixes issue #702
Wednesday, 19 June 2019
- [svgwg] Pull Request: Update link to default sizing algorithm. Fixes issue #702
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- [svgwg] Issue: Decide what to do with zoom and pan (#56) marked as Agenda+
- [svgwg] Issue: Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript (#291) marked as Agenda+
- [svgwg] Issue: Text with multiple x="" values should be shaped as if it was not broken (#631) marked as Agenda+
- Re: [svgwg] Define "svg layout box" vs "css layout box" (#703)
- Re: [svgwg] All links to "default sizing algorithm" are deadlink (#702)
- [svgwg] Issue: All links to "default sizing algorithm" are deadlink (#702) marked as Needs editing
- Re: [svgwg] Define "svg layout box" vs "css layout box" (#703)
- [svgwg] Pull Request: 'd' presentation attribute: use path() function
- Re: [svgwg] Define "svg layout box" vs "css layout box" (#703)
- [svgwg] Issue: A separate MIME type for svgz files is needed (#701) marked as Proposal
- Re: [svgwg] A separate MIME type for svgz files is needed (#701)
Monday, 17 June 2019
- Re: [svgwg] [svg-native] How should currentColor be handled? (#678)
- Re: [svgwg] SVG Extensions - IEC 61850-6-2 (#699)
- Re: [svgwg] Clarify Event attributes section (#467)
- Re: [svgwg] Define script element processing model (#196)
- Re: [svgwg] 'd' presentation attribute: use path() function (#374)
- Re: [svgwg] Clarify Event attributes section (#467)
- Re: [svgwg] Stroke alignment (#704)
- Re: [svgwg] Stroke alignment (#704)
- [svgwg] Stroke alignment (#704)
Sunday, 16 June 2019
- [svgwg] Issue: Define "svg layout box" vs "css layout box" (#703) marked as SVG2
- [svgwg] Define "svg layout box" vs "css layout box" (#703)
Thursday, 13 June 2019
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
Wednesday, 12 June 2019
Monday, 10 June 2019
- Re: [svgwg] [svg-native] How should currentColor be handled? (#678)
- Re: [svgwg] [svg-native] How should currentColor be handled? (#678)
- Re: [svgwg] 'd' presentation attribute: use path() function (#374)
- Re: [svgwg] Define script element processing model (#196)
Sunday, 9 June 2019
Saturday, 8 June 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)
- [svgwg] A separate MIME type for svgz files is needed (#701)
Friday, 7 June 2019
Thursday, 6 June 2019
- Re: [svgwg] Define script element processong model (#196)
- [svgwg] Issue: Clarify Event attributes section (#467) marked as Interactivity chapter
- Re: [svgwg] Define script element processong model (#196)
- [svgwg] Issue: Define script element processong model (#196) marked as Agenda+
- [svgwg] Issue: Identify SVG1 elements that are obsolete in SVG2 (#448) marked as Needs tests
- [svgwg] Issue: White-space only text nodes. (#352) marked as Needs editing
- [svgwg] Issue: What is the unit type after setting an SVGAngle or SVGLength's value (#478) marked as Needs editing
Wednesday, 5 June 2019
- Re: [svgwg] Text with multiple x="" values should be shaped as if it was not broken (#631)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
Tuesday, 4 June 2019
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
- Re: [svgwg] Decide what to do with zoom and pan (#56)
Monday, 3 June 2019
- Closed: [svgwg] mask-type is not listed as a presentational attribute in SVG spec (#692)
- Closed: [svgwg] Support transform-origin as a presentation attribute (#688)
- [svgwg] Merged Pull Request: Add transform-origin to list of presentation attributes. Fixes #688
- [svgwg] new commits pushed by AmeliaBR
- [svgwg] new commits pushed by AmeliaBR
- [svgwg] Merged Pull Request: Add mask-type to list of presentation attributes. Fixes issue #692
- [svgwg] Issue: SVG Extensions - IEC 61850-6-2 (#699) marked as Proposal