W3C home > Mailing lists > Public > public-svg-wg@w3.org > April to June 2010

Re: Reviewed filters-displacement-02-f.svg test

From: Erik Dahlstrom <ed@opera.com>
Date: Wed, 21 Apr 2010 21:14:42 +0200
To: "Chris Lilley" <chris@w3.org>
Cc: "public-svg-wg@w3.org" <public-svg-wg@w3.org>
Message-ID: <op.vbi02seageuyw5@erik-dahlstroms-macbook-pro-2.local>
On Wed, 21 Apr 2010 17:48:57 +0200, Chris Lilley <chris@w3.org> wrote:

> On Wednesday, April 21, 2010, 4:21:58 PM, Erik wrote:
> ED> Hi Chris,
> ED> I've reviewed your filters-displacement-02-f.svg testcase, adding  
> pass
> ED> criteria and some more testcase description text. Please verify that  
> the
> ED> changes are ok, I've marked the test as reviewed for now. I noted  
> that
> ED> firefox displayed the bottom gradient with a reddish tint applied  
> (making
> ED> it look different from the top gradient which is using essentially  
> the
> ED> same filter).
> Thanks, I will have a look (but am getting ready for another telcon at  
> the moment).
> ED> P.S. As a side-effect of reviewing, I also noticed that we had lost  
> some
> ED> information that was visible in the old 1.1 spec. Default values  
> that were
> ED> shown in the DTD snippets are not there anymore since we use the new  
> spec
> ED> style for elements. I updated the 1.1F2 spec to explicitly mention  
> the
> ED> default values for xChannelSelector and yChannelSelector [2].
> Ouch. We need to do a pass through the whole 1.1 spec looking for things  
> that depended on DTD defaulting.

Technically it's not a problem (for normativeness) since the information  
is still there in the DTD - but of course it's less accessible that way.  
It's nicer to present the information in the spec itself I agree, makes it  
harder to miss.

> On the other hand, the explicit prose is clearer and easier to  
> understand than reading a DTD snippet or schema snippet.
> Do we define 'lacuna value' in 1.1SE?

We don't, but there are at least a handful of places in the spec that say  
what happens if an attribute isn't specified.

Defining lacuna values for all attributes in SVG 1.1 would be very nice,  
but I think it's fine if that happens in the SVG 2.0 timeframe.


Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Wednesday, 21 April 2010 19:15:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:29:43 UTC