- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 13 Apr 2012 12:28:20 -0700
- To: Dirk Schulze <dschulze@adobe.com>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, "www-style@w3.org" <www-style@w3.org>
On Thu, Apr 12, 2012 at 8:39 PM, Dirk Schulze <dschulze@adobe.com> wrote: > I just want to make sure that specifying the parsing doesn't make current CSS parsers inflexible. For instance the CSS parser in WebKit can easily be modified to support the SVG parsing rules on transform lists for CSS Transforms [1] on SVG presentation attributes. This includes whitespaces between function names and the first opening brace, comma or whitspace separation of arguments or functions and so on. I wouldn't be happy to write the parser for transform functions twice. (Nearly) all browsers engines support scientific notations for numbers on SVG presentation attributes and like I wrote before: I bet no one implemented the CSS parser a second time just for SVG presentation attributes! The last part is the quirks mode. I am sure that no one wants to maintain a second parser for quirks mode. Even if just some properties differ. Therefore css3-syntax should be aware of all this. Where are rules like the "whitespace is allowed between function name and parenthesis" written? I can't find any detailed syntax descriptions in the SVG spec. ~TJ
Received on Friday, 13 April 2012 19:29:14 UTC