- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Wed, 10 Jan 2018 06:15:58 -0800
- To: Steven Pemberton <steven.pemberton@cwi.nl>
- Cc: XForms <public-xformsusers@w3.org>
What we do is: - hide the trigger if non-relevant (as we do for any other control) - show but disable the trigger if it is readonly We don't use any validity properties. If the bound node is invalid, would you show the trigger but disable its action? -Erik On Wed, Jan 10, 2018 at 3:15 AM, Steven Pemberton <steven.pemberton@cwi.nl> wrote: > > "Data Binding Restrictions: Binds to any node or an atomic value. This > control does not use the instance data it is bound to, but is affected by > the data's model item properties: the relevant property affects if the > control can be activated or not; all other properties have no effect." > > https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_trigger_Element > > I just wanted to check that we are OK with this. > > While preparing a test case, I noticed that at lease one implementation also > uses readonly. > (See > https://homepages.cwi.nl/~steven/forms/TestSuite/core/trigger-relevance.xhtml) > > However, what I noted while writing a recent form was that I want the > trigger only to work if the node it is attached to is 'ok' to use: > > * valid > * non-empty if required, and > * relevant. > > Any opinions? > > Steven. >
Received on Wednesday, 10 January 2018 14:21:17 UTC