- From: Jonathan Watt <jwatt@jwatt.org>
- Date: Mon, 01 Nov 2010 12:18:56 +0000
- To: Alex Danilo <alex@abbra.com>
- CC: Cameron McCormack <cam@mcc.id.au>, public-svg-wg@w3.org
Agreed. On 01/11/2010 03:26, Alex Danilo wrote: > Hi Cam, > > +1. > > I agree there's no point enforcing this, as we should > aim to be constent with CSS for this case (i.e. case insensitive). > > Alex > > --Original Message--: >> I am looking at types-basic-02-f.svg where one of the sub-tests checks >> that an attribute like stroke-width="20PX" has no effect, because the >> unit is in uppercase. Compare this with style="stroke-width: 20PX", >> which would work. >> >> I am wondering if there really is any value in enforcing this. It’s not >> like we will ever introduce units distinguished only by case. It seems >> that for consistency with specifying CSS properties in style sheets that >> we should just allow these to be case insensitive. >> >> What do you all think? >> >> -- >> Cameron McCormack ≝ http://mcc.id.au/ >> >> >> > > >
Received on Monday, 1 November 2010 12:19:03 UTC