Re[6]: [cgmo-webcgm] ISSUE: what does 'get..' return? [2 of 2]

[Benoit Bezaire <benoit@itedo.com>]

Hi Lofton,

Yes to all your questions! (That's how I interpret the CSS
specification.)

Regarding the 'Btw', I'm working on an email, I'll send it this
afternoon. Hopefully, it clarifies a few things.

-- 
 Benoit   mailto:benoit@itedo.com


Monday, May 9, 2005, 1:00:32 PM, Lofton wrote:

LH> To verify that I correctly understand all the technical details of theproposal...

LH> At 10:24 AM 5/9/2005 -0400, Benoit Bezaire wrote:
LH> Monday, May 9, 2005, 9:22:21 AM,Lofton wrote:

LH>> [...]  As I understand it, CV would be
LH>> the same as Specified Value for 'visibility' (and'inheritance').
LH> Not 100%, but I don't think it makes a big difference, ex:

LH> BEGAPS 'one'
LH>   ATTR 'visibility' 'on'
LH>   BEGAPS 'two'
LH>     ATTR 'visibility' 'inherit'
LH>     BEGAPS 'three'
LH>     ENDAPS
LH>   ENDAPS
LH> ENDAPS

LH> - 'one' has a clearly specified value of 'on', ok, the APS isvisible.
LH> - 'two' has a clearly specified value of 'inherit', but it's'computed
LH> value' (this is a CSS term) is 'on' (came from 'one'), 'two' is also
LH> visible.
LH> - 'three does not have a specified value, so it inherits the'computed
LH> value' of its parent which is 'on', not 'inherit'. (smalldistinction)


LH> (...and the *computed value* of 'three' is then 'on', correct?)

LH> So consider this modified example:

LH> BEGAPS 'one'
LH>   ATTR 'visibility' 'on'
LH>   BEGAPS 'two'
LH>     BEGAPS 'three'
LH>     ENDAPS
LH>     [...]
LH>   ENDAPS
LH> ENDAPS

LH> - 'one' has a clearly specified value of 'on', ok, the APS
LH> isvisible.  (And its Computed Value is 'on'.)
LH> - 'two' does not have a specified value, so it inherits the
LH> ComputedValue (this is a CSS term) of 'one', which is 'on'
LH> (because 'visibility'has "Inherited: yes" rule); 'two' is also
LH> visible.  (Andits Computed Value is 'on'.)
LH> - 'three' does not have a specified value, so it inherits the
LH> ComputedValue (this is a CSS term) of 'two', which is 'on'
LH> (because visibility'has "Inherited: yes" rule); 'three' is also
LH> visible.  (Andits Computed Value is 'on'.)

LH> That's all correct, right?  So the only detectable difference inthis example, is that
LH> ...getAppStructureById("two").getAppStructureAttr("visibility")
LH> returns 'inherit' in your original example, and empty string in my variant, correct?

LH> -Lofton.

LH> P.S.  Btw, for me at least, it is pretty hard to tease all of
LH> these subtleties out of 5.4.  Based on this thread (and the other
LH> about problems w/ "Style Attributes"), we should be able to
LH> identify some clarifying wording, and add some EXAMPLES!  (The
LH> latter suggestion might be considered for the whole of the spec,
LH> esp Ch.4 and Ch.5)