public-svg-wg@w3.org from January to March 2016 by subject

SVG-ACTION-3829: Clarify that getbbox on tspan/textpath includes only that element's glyphs, but that objectboundingbox values still are computed relative to the entire text element

• SVG Working Group Issue Tracker (Thursday, 14 January)

SVG-ACTION-3830: Draft a couple of sentences describing lat/long map data accuracy issue

• SVG Working Group Issue Tracker (Thursday, 14 January)

SVG-ACTION-3831: Add examples pointing out stroke painting inconsistencies between platforms, warning the author

• SVG Working Group Issue Tracker (Wednesday, 3 February)

SVG-ACTION-3832: Fix the linejoin algorithm to handle parallel miter-clip issue

• SVG Working Group Issue Tracker (Wednesday, 3 February)

SVG-ACTION-3833: Survey whether option 2 or 3 would be better for arcs fallback

• SVG Working Group Issue Tracker (Wednesday, 3 February)

SVG-ACTION-3834: Ask csswg if disallowing fill rule in path() for d is good

• Shane Stephens (Thursday, 4 February)
• Dirk Schulze (Thursday, 4 February)
• SVG Working Group Issue Tracker (Wednesday, 3 February)

SVG-ACTION-3835: Do thorough check on focus and tabindex in html and circle back with aria group on the results

• SVG Working Group Issue Tracker (Thursday, 4 February)

SVG-ACTION-3836: Add non-normative authoring guidance about content precision to conform.html

• SVG Working Group Issue Tracker (Friday, 5 February)

SVG-ACTION-3837: File a bug on chrome regarding zero length subpaths

• SVG Working Group Issue Tracker (Thursday, 18 February)

Last message date: Thursday, 18 February 2016 20:53:51 UTC