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: Ian Hickson [mailto:ian@hixie.ch] 

> On Thu, 11 May 2006, Scott Hayman wrote:
> > > 
> > > The problem is that an invalid IRI value is still 
> parsable and thus 
> > > does not get ignored at the parsing stage.
> > 
> > Right, but it can be ignored during the cascade.
> 
> I don't understand what it means to ignore something during 
> the cascade. 
> This is not a concept that is present in CSS.

I think that I now understand the issue.  Thanks for the clarification.

> The wording of the spec as it stands does not explain what it means.

Looking at the part of the CSS 2.1 spec that talks about url() property
values [1], it seems as if it is left up to the UA as to how to handle
invalid URIs or URIs that designate unavailable or inapplicable
resources.  The SVG working group would like to specify this behaviour,
so it doesn't look like we will be able to just refer to the CSS spec in
this matter.

Given what we are trying to do, would it be correct to say that the
computed value of the property is as if it had been inherited?  I know
that this may not be 100% correct spec terminology, but I'm just trying
to get agreement on the concept using CSS terminology.  

Is this the correct CSS terminology to capture this concept?  If not,
would you be able to propose something?

Thanks very much for your help in sorting out this section of the spec.

Regards,
Scott

[1] http://www.w3.org/TR/CSS21/syndata.html#uri



---------------------------------------------------------------------
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 Thursday, 11 May 2006 10:11:59 UTC