Incremental input does not work on dynamically inserted input fields referencing data type xs:time

Hi,

I think I found a bug concerning input fields that reference dynamically inserted data bound to type xs:time. On those fields, the incremental input does not work.

In the attached file "timetest.xhtml" I have added an easy example:
The page contains a table with 3 columns, a column 'From', a column 'to' and a column 'Difference' (attribute total).
My default instance looks like this:
          </times>
     </xf:instance>
With the following binds:
     <xf:bind ref="instance('times')/time/@from" type="xs:time" />
     <xf:bind ref="instance('times')/time/@to" type="xs:time" />
     <xf:bind ref="instance('times')/time/@total" type="xs:duration"
                         else (xs:time(../@to) - xs:time(../@from)))" />
My table has a xhtml:tr repeat on nodeset instance('times')/time. Each repeated row shows two input fields (for attributes @from and @to) and an output field that shows the calculated duration (attribute @total).

I then have a button that inserts an extra time element:
The action on the button looks like this:
At first at didn't have the recalculate and the rebuild, but that did not work either.

Now what is the problem:

• If you type in a time in one of the time input fields of the first row, the duration bind is immediately calculated. This is because the row was present in the default instance on load.
• If you insert a new row and type in a time in one of the input fields of the new row, then the duration is not calculated until you click outside the input field. It seems like the inserted input field does not react to incremental changes, even if the 'incremental' attribute (set to true) is added to the input field. Even a recalculate and rebuild after the insert does not fix this problem.

I have a more advanced example that uses autosave and allows you to load previously entered instance data. If you load a from with instance data that has previously inserted rows in it, then the problem does not occur on those rows after the load. However, newly inserted rows still have the same problem.
I played around a bit with other input types like text input, but there is no problem with the increment there.

I hope you can give me some input on this.

Thanks in advance,

Toon Andries
Professional Services Consultant
Inventive Designers

Thank you for the quick response!
We will update our Orbeon and I will let you know when I have tested this issue.

Kind regards,
Toon