> Hi,
>
>> Wow - this is a nice catch. I couldn't believe my eyes. This is indeed
>> a bug (not too much of a surprise so far), but this one has been
>> introduced in a refactoring done in November 2008. Here is the
>> relevant section of that 2008 commit:
>>
>> http://github.com/orbeon/orbeon-forms/commit/547d4776bc7077ba434d9978eea8c6
>> 2688bd42ac#L0R2316
> Wow, glad you found that out :)
>
>> I checked all the other changes done at that time (you never know!),
>> and this one was the only faulty one. So I fixed this, and the fix
>> will be in the next nightly build. For reference, the bug is:
>>
>> http://forge.ow2.org/tracker/index.php?func=detail&aid=315584&group_id=168&
>> atid=350207
>>
>> You'll let us know how the new build works for you.
> I solved the problem in the mean time by using xxforms:script. This also
> allowed to be get the behaviour that I actually wanted - to update the form
> not some fixed time span after the first key press, but some time span after the
> last. So, pressing a key every 100ms, 10 times in a row, should only result in
> one update after the last keystroke. Is this possible with the built-in
> settings? Besides, I am hesitant to use a nightly build in production.
>
> I'll try to do a quick test of the nightly later this week.
>
> Kind regards,
> Ralf Jung
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>