- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Wed, 10 Jan 2018 12:56:31 -0800
- To: Steven Pemberton <steven.pemberton@cwi.nl>
- Cc: XForms <public-xformsusers@w3.org>
>> - hide the trigger if non-relevant (as we do for any other control) >> - show but disable the trigger if it is readonly > > That is what XSLTForms does as well. I don't quite get the reasoning behind > disabling the action on readonly though. Controls in various environments, including HTML, typically have a "disabled" mode, where they appear but otherwise don't work. This is true for input fields, dropdowns, etc. Buttons too have such a mode. When an input control is readonly it makes sense to show it as disabled (although there could be a subtle difference between the two). So by extension using `readonly` as the way to make the button look disabled seems a natural way given the MIPs available right now in XForms. >> We don't use any validity properties. If the bound node is invalid, >> would you show the trigger but disable its action? > > > Yes; also if it is required and empty. Ok. -Erik
Received on Wednesday, 10 January 2018 20:57:13 UTC