- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 May 2018 19:21:29 +0000
- To: public-css-archive@w3.org
@tabatkins the question to you was specifically to supporting `<funtion-name> wsp* ( <content> )`. Sounds like you confirmed that this won’t be possible. IIRC, this would be the only incompatibility for tokenization to the [SVG BNF](https://www.w3.org/TR/SVG11/coords.html#TransformAttribute) for transforms now. (Support for scientific numbers is part of CSS.) Browser would need to agree to remove this requirement from SVG transforms before it makes sense to discuss possible other differences between the transform attribute and other ways of setting the transform property. (Different set of supported transform functions, difference between the rotate transform function specifically.) The requested from @longsonr is currently not supported by the SVG spec but could be with CSS. @longsonr @smfr @dstorey @boggydigital (not sure who to add for Blink @chrishtr maybe?) any comment on disallowing white spaces between transform function name and opening parentheses for transform attribute which would allow us to require CSS parsing rules even on the transform attribute? Any way we can gather data about possible usage today? -- GitHub Notification of comment by dirkschulze Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2623#issuecomment-386091120 using your GitHub account
Received on Wednesday, 2 May 2018 19:21:32 UTC