- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Thu, 13 Jun 2024 17:05:23 -0700
- To: Steven Pemberton <steven.pemberton@cwi.nl>
- Cc: XForms <public-xformsusers@w3.org>
Received on Friday, 14 June 2024 00:05:39 UTC
Regarding disabling the trigger for other MIPS, I don't have a strong feeling about it. In general, a trigger bound to a node will not be bound to a node that contains data and validation, I think, but of course it could. Regarding DOMActivate, I am not sure if the trigger needs to respond to that event: instead, the user agent/XForms processor dispatches DOMActivate. If the trigger is non-relevant or disabled, the user agent/XForms processor will not dispatch a DOMActivate event. On Tue, Jun 11, 2024 at 6:09 AM Steven Pemberton <steven.pemberton@cwi.nl> wrote: > By the way, the spec says: > > > - the relevant property affects visibility, focus, and navigation > order as with other controls, and thus disables the trigger; > - the readonly property has a similar effect as with input controls: > the trigger cannot receive focus, cannot be activated, but remains visible > with a presentation that indicates it is not activatable; > > > I'm assuming that "not activatable" for these two includes not responding > to DOMActivate being dispatched to it. Do we agree? > > Steven >
Received on Friday, 14 June 2024 00:05:39 UTC