- From: Dirk Schulze <dschulze@adobe.com>
- Date: Wed, 23 May 2012 07:11:26 -0700
- To: Cameron McCormack <cam@mcc.id.au>
- CC: SVG public list <www-svg@w3.org>
I would rather limit the differences instead of increasing them. Like discussed before, browsers already use the CSS parser for presentation attributes but with special casing on presentation attributes. Instead we should support Tab's idea to support scientific notations and unit less values in CSS in general, so that we don't need to special casing anymore. How could comments in presentation attribute increase readability? Why no comment in or before the element? Same syntax in SVG as well as in CSS! Dirk Sent from my iPhone On May 22, 2012, at 10:22 PM, "Cameron McCormack" <cam@mcc.id.au> wrote: > I just mentioned in > http://lists.w3.org/Archives/Public/www-style/2012May/0830.html that > implementations (unsurprisingly) differ in whether they accept CSS-style > comments and escapes in presentation attributes. In the spirit of > reducing the differences between values in presentation attributes and > style sheet declarations (and remember that we have already agreed to > remove the case sensitivity of them), what do people think about > allowing comments and escapes in presentation attributes? > > Once css3-syntax is a bit further fleshed out, we could invoke the > parser it defines, using flags that allow the slightly different SVG > syntax that we still need (unitless lengths, scientific notation). >
Received on Wednesday, 23 May 2012 14:12:05 UTC