- From: Chris Lilley <chris@w3.org>
- Date: Tue, 2 Jun 2009 21:35:18 +0200
- To: public-svg-wg@w3.org
Hello , I noticed that I have ACTION-2525 Add an item to the F1.1 errata that allows case insensitivity for the 'RGB' value when painting I have checked in a draft erratum that fixes this which is trivial. The erratum is marked as draft. If its ok, and can be agreed on Wednesday, please assign me an action to bump it to proposed and to add the change to the 1.1 Second Edition document. Here is the description, the resolution, and the changed text (trimmed to the smallest part that actually changed): description: CSS2, the origin of the rgb() functional notation, allows this to be case insensitive. Implementations allow it to be case insensitive in stylesheets, but vary in what they allow for presentation attributes (lowercase only, lower or upper case, mixed case ...). resolution: For consistency with implementations and deployed content, the functional notation was made case insensitive; and for maximal compatibility with existing implementations, the lowercase form rgb() is preferred. change from: The format of an RGB value in the functional notation is 'rgb(' followed by a comma-separated list of three numerical values (either three integer values or three percentage values) followed by ')'. change to: The format of an RGB value in the functional notation is an RGB start-function followed by a comma-separated list of three numerical values (either three integer values or three percentage values) followed by ')'. An RGB start-function is the case-insensitive string 'rgb(' - so for example 'RGB(' or 'rGb('. For compatibility, the all-lowercase form 'rgb(' is preferred. -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Tuesday, 2 June 2009 19:36:16 UTC