Re: CSS level errors.

I have a few observations:

1) If an ICC color specification is incorrect (defined either via the 
language or via the DOM), then the user agent should default to the sRGB 
color values, assuming that part of the color specification is correct. 
Thus, I would maintain that an invalid ICC color specification should not 
by itself put the document in an error state. (The spec should probably 
state this explicitly.)

2) There are more cases than just an empty list that could cause a list of 
color values to be invalid. For example, what if a profile requires 6 color 
values (e.g., hexachrome) or 4 (e.g., CMYK), and only 3 color values are 
provided? Or what if too many color values are provided? My opinion is that 
the implementation should ignore the entire ICC color specification if the 
wrong number of values are provided or if any of these values are somehow 
invalid, and fall back to the sRGB color values.

3) What other exceptions are you thinking of regarding 'colorProfile'? It 
is just a string. The only thing that can go wrong is that the string 
doesn't match any previously defined profiles, in which case the ICC color 
specification should be ignored and the sRGB used instead.


At 10:49 AM 8/25/00 -0700, Blaine Brodie wrote:
>If it is not acceptable for CSS properties to go in error via calls to the
>SVG's CSS level method calls, then there are a few problems using the
>SVGICCColor interface to manipulate SVGColor property data.
>   - 'colorProfile' does not throw a SYNTAX_ERR exception on setting.
>   - SVGICCColor contains a SVGList.  SVGList contains a 'clear' method
>which removes all the items from the list, however an icc-color must
>always contain one value.  A similiar problem exists when one attempts to
>remove the final item from a list using the 'removeItem' method.

Received on Wednesday, 30 August 2000 17:35:07 UTC