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

Re: SVG12: getTrait vs 'display' property

From: Jon Ferraiolo <jonf@adobe.com>
Date: Thu, 16 Mar 2006 12:41:06 -0800
Message-ID: <6ECA24BE410D994496A2AE995367C5C8891BC6@namail3.corp.adobe.com>
To: "Chris Lilley" <chris@w3.org>
Cc: <www-svg@w3.org>
Hi Chris,

I believe it is the correct approach for the 'display' property to work as follows:


*	SVG Tiny UAs are granted the ability to normalize the property value (which allows for simplified implementations for small devices)
*	Inheritance passes through whatever value was entered, which provides for UAs to achieve lossless information through inheritance  (i.e., unless normalization has happened with Tiny UAs). For example, display=block can pass the string "block" to children.
*	UAs are required to return only the "normalized" values (i.e., "inline" or "none") via the trait getters, which allows for straightforward scripting via traits.


I think this is a good tradeoff between SVG's limited use of the 'display' property, the constraints of devices for which SVG Tiny is targeted, and requirements for future compound document scenarios.


This is what I see in the latest working group draft (which I can see, since I am in the WG), so I am happy. Your response below, re-inforced by what I see in the draft, therefore satisfies my concerns. 





From: Chris Lilley <chris@w3.org <mailto:chris@w3.org?Subject=Re:%20SVG12:%20getTrait%20vs%20%27display%27%20property&In-Reply-To=%3C293777353.20050922115204@w3.org%3E&References=%3C293777353.20050922115204@w3.org%3E> > 
Date: Thu, 22 Sep 2005 11:52:04 +0200
Message-ID: <293777353.20050922115204@w3.org> 
To: Bjoern Hoehrmann <derhoermi@gmx.net <mailto:derhoermi@gmx.net?Subject=Re:%20SVG12:%20getTrait%20vs%20%27display%27%20property&In-Reply-To=%3C293777353.20050922115204@w3.org%3E&References=%3C293777353.20050922115204@w3.org%3E> > 
Cc: www-svg@w3.org <mailto:www-svg@w3.org?Subject=Re:%20SVG12:%20getTrait%20vs%20%27display%27%20property&In-Reply-To=%3C293777353.20050922115204@w3.org%3E&References=%3C293777353.20050922115204@w3.org%3E>  
On Monday, July 4, 2005, 4:27:58 AM, Bjoern wrote:
BH> Dear Scalable Vector Graphics Working Group,
BH>   In http://lists.w3.org/Archives/Public/www-svg/2005Jun/0058 Jon
BH> Ferraiolo raised an issue on how getTrait and the 'display' property
BH> interact. He points out that the interactions of these facilities
BH> are easy to overlook by implementers; please change the draft such
BH> that these are not easy to overlook. He also requests that this is
BH> tested for in the SVG Tiny 1.2 test suite, please add such a test
BH> to the test suite.
Hi Björn, Jon
We have changed the draft such that the computed value of the display
property, on the one hand, and the value returned by getTrait on the
display property are clearly distinguished. This allows the full range
of computed values (block, inline etc) to inherit to child elements
which may make use of them, and allows getTrait to return the only two
values that affect SVG rendering.
We will add a test to the 1.2 test suite.
Please let us know if this does not satisfy your joint comment.
 Chris Lilley                    mailto:chris@w3.org <mailto:chris@w3.org?Subject=Re:%20SVG12:%20getTrait%20vs%20%27display%27%20property&In-Reply-To=%3C293777353.20050922115204@w3.org%3E&References=%3C293777353.20050922115204@w3.org%3E> 
 Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG

Received on Thursday, 16 March 2006 21:53:42 UTC

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