I noted that when you have a schema.List and (auto-)add a new row to your Datagrid, the orderedselect_input JS code raises an alert (Must select something) when you try to select value(s) :
This is caused by the JS code of the widget which is called from the template with input ID as argument.
When a new row is added to Datagrid, attributes such as name, href, etc. on child elements (that contain the row index) are fixed. But of course the JS code chunks remain the same, for example :
<button onclick="javascript:from2to()"
name="from2toButton" type="button" value="→"
tal:attributes="onClick string:javascript:from2to('${view/id}')"
>→</button>
The row referred in JS code no longer matches the new Datagrid row anymore and all calls like from2to('${view/id}') will cause issues.
I noted that when you have a
schema.Listand (auto-)add a new row to your Datagrid, the orderedselect_input JS code raises an alert (Must select something) when you try to select value(s) :This is caused by the JS code of the widget which is called from the template with input ID as argument.
When a new row is added to Datagrid, attributes such as name, href, etc. on child elements (that contain the row index) are fixed. But of course the JS code chunks remain the same, for example :
The row referred in JS code no longer matches the new Datagrid row anymore and all calls like
from2to('${view/id}')will cause issues.