W3C home > Mailing lists > Public > www-forms@w3.org > December 2003

RE: xforms for inhomogenous collections

From: Borgrink, Susan <sborgrink@progeny.net>
Date: Thu, 18 Dec 2003 15:48:29 -0500
Message-ID: <FB041607EAE6DF4697B73E29142D1C4B01554F@es3.progeny.net>
To: "m b" <Mark.Birbeck@x-port.net>
Cc: "Oliver Scholz " <alkibiades@gmx.de>, <www-forms@w3.org>
Mark, 

  I apologize for any confusion, but what I stated was how I interpreted this line from the specification for the relevant property section 6.1.4.

"Inheritance Rules: If any ancestor node evaluates to XPath false, this value is treated as false. Otherwise, the local value is used."

  If that is not the case can you please explain to me what this statement means.

  Though in your example, I overlooked the CSS portion, the CSS would do the same thing.

Susan 

-----Original Message-----
From: m b [mailto:Mark.Birbeck@x-port.net]
Sent: Thursday, December 18, 2003 3:29 PM
To: Borgrink, Susan
Cc: 'Oliver Scholz '; 'www-forms@w3.org '
Subject: RE: xforms for inhomogenous collections


Susan,

> Mark was pointing you in the right direction ...

I was, but now you're taking people in the wrong one ;-)

> ... the relevant attribute is used within the bind element rather
> than the in form control.  However, what may not have been evident
> before and what may help to tie some of this all together is that
> the relevant attribute is inheritable. Therefore, whatever is a
> child of the group element would be tied to its relevance.

It wasn't evident because it isn't true. You are mixing up two things - the
UI and the model. All descendants of 'page[1]' in the instance data would
indeed be disabled if 'page[1]' was disabled (provided that they themselves
didn't have a @relevant rule that overrode this), and that is what the spec
means when it says that @relevant is inheritable. But that has nothing to do
with the descendants of xf:group.

You can only affect the descendents of xf:group with CSS - which is what my
example was showing. You wrote:

> As Mark's example showed:
>
> ...
> <xforms:group ref="page[1]">
>   <h2><xforms:output ref="@title" /></h2>
>   I'm the first page ...
> </xforms:group>
> ...
>
> the output would be tied to the parent goup element.

but the reason the xf:output gets hidden is because the CSS style on
xf:group is automatically set to 'display: none;' when the node that the
xf:group is bound to becomes disabled - as determined by the rule in the
@relevant model item property. This means that any markup inside the
xf:group will be hidden, but we need to be clear that this is thanks to CSS,
and not the XForms model.

Regards,

Mark


Mark Birbeck
CEO and CTO
x-port.net Ltd.

For 100% of the XForms spec:
http://www.formsPlayer.com/

Received on Thursday, 18 December 2003 15:48:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:56 GMT