W3C home > Mailing lists > Public > www-svg@w3.org > June 2006

RE: SVGMobile12] SVGT12-183: Rules for handling "unsupported" values don't work when properties are syntactically correct and specified using W3C mechanisms other than SVG attributes

From: Scott Hayman <shayman@rim.com>
Date: Mon, 5 Jun 2006 08:46:25 -0400
Message-ID: <1CA55DCF91707745A9B5091A303367E904AD99A5@XCH43YKF.rim.net>
To: "Ian Hickson" <ian@hixie.ch>
Cc: <www-svg@w3.org>

Hi Ian, 

> From: Ian Hickson [mailto:ian@hixie.ch] 
> Sent: May 11, 2006 6:37 AM

> The only real option I can see is to give a value, e.g. 
> 'none', and require that if the URI is not valid, then that 
> value must be used instead. It's too late, by time the time 
> you have this property, to base it on other values of that 
> property that the author may have specified (e.g. on the 
> parent element or in stylesheets).

After discussing this in the SVG WG, we've agreed that the above is the
best approach to take.  The spec will be changed to say that unsupported
values of <paint> must be treated as if 'none' was specified.

Thanks very much for your help in sorting out this issue.  Please let us
know within 2 weeks if this does not address your concern.

Regards,
Scott



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Monday, 5 June 2006 12:46:35 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:34 GMT