{"push_id":770614657,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"cf0a04a555164724d1a6b789266c314fbdebcbdf","before":"f504b325370e308b370e03905c43594b54563f57","commits":[{"sha":"cf0a04a555164724d1a6b789266c314fbdebcbdf","author":{"email":"08820338a18455d35544f526db3e9a6acb9d6d5e@gmail.com","name":"Bogdan Brinza"},"message":"[linking] Addressing issues 6,7 and 8\n\nUsed the opportunity to clean the paragraph SVG fragment identifiers to\nintroduce a bit more structure and break the wall of text.\n\nIssue 6 - Referenced CSS Transforms spec and as discussed on Paris 2015\nF2F meeting spec'd that svgView parameters apply in definition sequence\n\nIssue 7 - As discussed and agreed on Paris 2015 F2F meeting at this\npoint we don't want to bring addition transform parameters and styles\n(such as transform-origin, perspective, preserve-3d). Based on the\nfurther feedback we'll consider those changes in the future.\n\nIssue 8 - Reflected actual browser support. Spaces are supported in all\nbrowsers (and we couldn't identify obvious reason they shouldn't) and\nsemicolon escaping in not supported in WebKit/Blink but we've discussed\nthat URL fragment processing should adhere to general URL processing\nrules and referenced escaping rules.","distinct":true,"url":"https://api.github.com/repos/w3c/svgwg/commits/cf0a04a555164724d1a6b789266c314fbdebcbdf"}]}