- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Tue, 12 Jun 2018 09:26:07 -0700
- To: Steven Pemberton <steven.pemberton@cwi.nl>
- Cc: XForms <public-xformsusers@w3.org>
Received on Tuesday, 12 June 2018 16:26:41 UTC
Maybe because we had the (now deprecated) nested elements to dynamically set those values? It seems to me that we do want to require `name` and `targetid`. On Tue, Jun 12, 2018 at 2:44 AM Steven Pemberton <steven.pemberton@cwi.nl> wrote: > And @targetid is optional too. > > Why? > > (Apart from me wanting the default to be the current or parent element, > but that's a different issue > https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0009) > > Steven > > > On Tue, 12 Jun 2018 11:39:53 +0200, Steven Pemberton > <steven.pemberton@cwi.nl> wrote: > > > > https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_dispatch_Element > > > > Special Attributes: > > name > > Optional string giving the name of the event to dispatch. > > > > Why is this optional? > > > > Is there any case where it is not needed? What happens if it is not > > supplied? > > > > Steven > >
Received on Tuesday, 12 June 2018 16:26:41 UTC