W3C home > Mailing lists > Public > public-xformsusers@w3.org > December 2018

Re: ACTION-2207: Merge <signal/> into <dispatch/>

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Wed, 12 Dec 2018 12:51:51 +0100
To: public-xformsusers@w3.org, "XForms Users Community Group Issue Tracker" <sysbot+tracker@w3.org>
Message-ID: <op.ztwq8pjnsmjzpq@steven-xps>
To summarise the current situation:

Requirements

To add the ability to be able to dispatch events into and out of an  
embedded XForms.

Original proposal

*  Use a different control that models <dispatch/>, but is solely for  
embedding.
    To dispatch an event into an embedding, you use

       <signal name="event-name" control="embedding-control-id"/>

    To dispatch an event out of an embedding, you use

       <signal name="event-name"/>

New proposal

*  Merge <signal/> into <dispatch/>
    To dispatch an event into an embedding, you use
       <dispatch name="event-name" control="embedding-control-id"/>
    The event goes to the first model of the embedded XForm

    To dispatch an event out of an embedding, you use
       <dispatch name="event-name"/>
    (The absence of @targetid or @control implies that it is dispatched to  
the embedder).
    The event goes to the <control/> element that caused the embedding.

Steven

On Wed, 07 Nov 2018 15:19:52 +0100, XForms Users Community Group Issue  
Tracker <sysbot+tracker@w3.org> wrote:

> ACTION-2207: Merge <signal/> into <dispatch/>
>
> https://www.w3.org/2005/06/tracker/xforms/actions/2207
>
> Assigned to: Steven Pemberton
Received on Wednesday, 12 December 2018 11:52:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 12 December 2018 11:52:38 UTC