RE: [SVGMobile12] more on data types

I also agree with this. I believe the spec is clear that *all* invalid
attribute values are ignored and I don't think that is much of a burden,
even for tiny implementers. Regarding what should be in the test suite I
think the more the better but IMO that shouldn't be discussed in the
scope of LC-spec-comments.

/ola

 

 

 

From: Jon Ferraiolo <jonf@adobe.com
<mailto:jonf@adobe.com?Subject=RE%3A%20%5BSVGMobile12%5D%20more%20on%20d
ata%20types&In-Reply-To=%253C6ECA24BE410D994496A2AE995367C5C8576B75%40na
mail3.corp.adobe.com%253E&References=%253C6ECA24BE410D994496A2AE995367C5
C8576B75%40namail3.corp.adobe.com%253E> > 
Date: Tue, 10 Jan 2006 17:16:01 -0800
Message-ID:
<6ECA24BE410D994496A2AE995367C5C8576B75@namail3.corp.adobe.com> 
To: "Eric Seidel" <eseidel@apple.com
<mailto:eseidel@apple.com?Subject=RE%3A%20%5BSVGMobile12%5D%20more%20on%
20data%20types&In-Reply-To=%253C6ECA24BE410D994496A2AE995367C5C8576B75%4
0namail3.corp.adobe.com%253E&References=%253C6ECA24BE410D994496A2AE99536
7C5C8576B75%40namail3.corp.adobe.com%253E> > 
Cc: "Maciej Stachowiak" <mjs@apple.com
<mailto:mjs@apple.com?Subject=RE%3A%20%5BSVGMobile12%5D%20more%20on%20da
ta%20types&In-Reply-To=%253C6ECA24BE410D994496A2AE995367C5C8576B75%40nam
ail3.corp.adobe.com%253E&References=%253C6ECA24BE410D994496A2AE995367C5C
8576B75%40namail3.corp.adobe.com%253E> >, "Bjoern Hoehrmann"
<derhoermi@gmx.net
<mailto:derhoermi@gmx.net?Subject=RE%3A%20%5BSVGMobile12%5D%20more%20on%
20data%20types&In-Reply-To=%253C6ECA24BE410D994496A2AE995367C5C8576B75%4
0namail3.corp.adobe.com%253E&References=%253C6ECA24BE410D994496A2AE99536
7C5C8576B75%40namail3.corp.adobe.com%253E> >, <www-svg@w3.org
<mailto:www-svg@w3.org?Subject=RE%3A%20%5BSVGMobile12%5D%20more%20on%20d
ata%20types&In-Reply-To=%253C6ECA24BE410D994496A2AE995367C5C8576B75%40na
mail3.corp.adobe.com%253E&References=%253C6ECA24BE410D994496A2AE995367C5
C8576B75%40namail3.corp.adobe.com%253E> > 

Eric,
 
I agree with your analysis, particularly with respect to the transform
attribute. (And if other implementers agree with Maciej, for other
attributes as well.)
 
 
 
The SVG WG should have a test for the 'tranform' attribute for incorrect
entries such as the example you provide. It is too much to ask for tests
for every possible incorrect formulation of every attribute, but the
example you give below represents a case which is more likely due to
accidental error, such as misspelling 'translate'.
 
 
 
Jon
 
________________________________
 
From: Eric Seidel [mailto:eseidel@apple.com
<mailto:eseidel@apple.com?Subject=RE%3A%20%5BSVGMobile12%5D%20more%20on%
20data%20types&In-Reply-To=%253C6ECA24BE410D994496A2AE995367C5C8576B75%4
0namail3.corp.adobe.com%253E&References=%253C6ECA24BE410D994496A2AE99536
7C5C8576B75%40namail3.corp.adobe.com%253E> ] 
Sent: Tuesday, January 10, 2006 5:05 PM
To: Jon Ferraiolo
Cc: Maciej Stachowiak; Bjoern Hoehrmann; www-svg@w3.org
<mailto:www-svg@w3.org?Subject=RE%3A%20%5BSVGMobile12%5D%20more%20on%20d
ata%20types&In-Reply-To=%253C6ECA24BE410D994496A2AE995367C5C8576B75%40na
mail3.corp.adobe.com%253E&References=%253C6ECA24BE410D994496A2AE995367C5
C8576B75%40namail3.corp.adobe.com%253E> 
Subject: Re: [SVGMobile12] more on data types
 
 
 
My understanding is that invalid attribute values are "unknown" and thus
are ignored completely.
 
 
 
C.2 Unsupported elements, attributes, properties, attribute values and
property 
 
values 
 
Conforming SVG User Agents must ignore unknown attributes, attribute
values, styling properties, styling property 
 
values, and descendant elements as follows: 
 
 
 
Am I reading this correctly?
 
 
 
Thus things like transform="scale(2) foobar(2) translate(2,3)" should be
ignored completely.  (This has been brought up before and is an area
where FireFox and Safari currently disagree.)
 
 
 
-eric