W3C home > Mailing lists > Public > public-xformsusers@w3.org > May 2019

Re: ACTION-2257: Define xforms-replace event

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Thu, 23 May 2019 10:06:44 -0700
Message-ID: <CAAc0PEVGDMZ1QPT6VX_9-uFbSh9bieiMp2JTdYWwApq6+VJBhw@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: XForms <public-xformsusers@w3.org>, XForms Users Community Group Issue Tracker <sysbot+tracker@w3.org>
> The node whose content has been replaced

The action doesn't replace content but replaces the nodes themselves. I
suggest, by consistency with `xforms-delete`: [1]

    The instance data node or nodes replaced. Note that these nodes are no
longer referenced by their parents.

To consider separately, we could, instead, have two pieces of information:

- `deleted-nodes`
- `inserted-nodes`

This would make things consistent with xforms-insert/xforms-delete.

In case an atomic value is used for insert/replace, we'd have to see what
we do since text nodes might not correspond directly to atomic values (see
XDM). Maybe it would be better to have:

- `deleted-nodes` or `replaced-nodes` (as items cannot be deleted or
replaced, I *think*)
- `inserted-items`

But then we would lose consistency unless we also add `inserted-items` to
`xforms-insert`.

-Erik

[1]
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-delete_Event

On Thu, May 23, 2019 at 7:38 AM Steven Pemberton <steven.pemberton@cwi.nl>
wrote:

> 13.3.x The xforms-replace Event
>
> This notification event is dispatched after successful execution of a
> replace action.
>
> Target: instance Bubbles: Yes Cancelable: No
>
> Context Info:
>
> replaced-node (node-sequence)
>         The node whose content has been replaced.
>
>
> On Wed, 22 May 2019 15:07:05 +0200, XForms Users Community Group Issue
> Tracker <sysbot+tracker@w3.org> wrote:
>
> > ACTION-2257: Define xforms-replace event
> >
> > https://www.w3.org/2005/06/tracker/xforms/actions/2257
> >
> > Assigned to: Steven Pemberton
>
>
Received on Thursday, 23 May 2019 17:07:19 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 23 May 2019 17:07:20 UTC