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

Re: ACTION-2121 - Reformulate text for @incremental

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Tue, 16 May 2017 09:30:46 -0700
Message-ID: <CAAc0PEWmTEOGjGbGtcFEtcnyTVozs08UHUAGpcxRSnPg-NKCFg@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
+1 and LGTM.

-Erik

On Tue, May 16, 2017 at 7:28 AM, Steven Pemberton <steven.pemberton@cwi.nl>
wrote:

> It seems to me that the distinction between incremental and
> non-incremental is
>
> * non-incremental: the instance gets updated when the control loses focus
> * incremental: the instance gets updated immediately.
>
> This leads me to think that it is wrong to say that the default value for
> @incremental is 'false': it seems better to say that it is different per
> control, and per modality.
>
> So here is a proposed text for @incremental:
>
> <<<<
> incremental
> Author-optional attribute that determines when a bound control updates
> instance data.
>
> Normally, controls that only require a single interaction update the
> instance immediately when a change is made; controls that require more
> interaction, like text-oriented controls such as <code>textarea</code>,
> only update the instance once focus is moved away.
>
> When false, this attribute indicates that the instance data should be
> updated when the control loses focus; when true, the instance data should
> be updated more often, thereby generating more xforms-value-changed events.
> When true, an implementation may buffer sequences of changes happening in
> quick succession, and apply them all at once.
>
> The default value for this attribute varies per control, and possibly per
> modality, but for textual controls the default is normally false.
>
>>
>>>>>
> Steven
>
>
Received on Tuesday, 16 May 2017 16:31:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:37:48 UTC