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

RE: [SVGMobile12] more on data types

From: Jon Ferraiolo <jonf@adobe.com>
Date: Tue, 10 Jan 2006 14:38:46 -0800
Message-ID: <6ECA24BE410D994496A2AE995367C5C8576ADB@namail3.corp.adobe.com>
To: "Anne van Kesteren" <fora@annevankesteren.nl>, <www-svg@w3.org>

Thanks for the good research.

It seems to me that there are two reasonable ways to go:

(1) Ian's model of having different syntax requirements for SVG's
"presentation attributes" (i.e., properties expressed as XML attributes)
than for CSS stylesheets. In this scenario, a value of "RED" for an XML
attribute would be incorrect content whereas a value of "RED" within a
stylesheet would work.

(2) Unify the syntax for SVG's presentation attributes with the syntax
used by properties contained within stylesheets. [But this gets us back
into the unitless values discussion and other thorny questions.]

It is sounding like most everyone is saying (1) is reasonable and also
it is sounding like we can't agree on how the unification approach for
(2) should work, and therefore Ian's proposal is looking good.

If we go for (1), then SVG needs to add at least one test to the test
suite which makes sure that implementations do not accept
case-insensitive keyword values for presentation attributes. (That is,
"RED" must not work within a presentation attribute.)


-----Original Message-----
From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] On Behalf
Of Anne van Kesteren
Sent: Tuesday, January 10, 2006 12:39 PM
To: www-svg@w3.org
Subject: [SVGMobile12] more on data types

I created some simple testcases to check how attribute values are
parsed in current browsers:

The first tests case-sensitive matching. In theory the testcase square
should be
"black" (the initial value), but in Opera, Mozilla and Internet Explorer
the Adobe plugin it is "RED". The same is true for the second testcase,
three render the value " red" as "red".

Given that CSS allows case-insensitive matching I'm not sure how you
could use
the parser for these color values. For CSS values it is also doesn't
matter if they are preceded by a space.

I'm wondering if the SVG WG could describe error handling that more
matches what is actually implemented as what is implemented is probably
used. Also, are things like:

# style="FiLL:ReD"

... allowed? In other words, should inside the "style" attribute and
elements normal CSS rules apply?

It should at least become more clear how to _exactly_ parse such
values. (This is different from describing how they can be used.)
that is not entirely clear to me.

Anne van Kesteren
Received on Tuesday, 10 January 2006 22:37:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:06 UTC