Wrong id and error maxlenght in orbeon 3.7.1

In element repeat I have input:

<xf:repeat id="rid" nodeset="instance('persons')/sl:person" appearance="full">
   <xf:input id="i-name" ref="sl:name" <b>xxf:maxlength="320">
   </xf:input>
</xf:repeat>

and triger:

<xf:trigger>
        <xf:label ref="..."/>       
        <xf:action ev:event="DOMActivate">
                <xf:insert bind="b-person" at="index('rid')" position="after" origin="instance('persons-temp')/sl:person" ev:event="DOMActivate"/>
        </xf:action>
</xf:trigger>

At the beginning, first element in the html looks like this:

<input <b>id="i-name·1$xforms-input-1" ... maxlength="320" />

When I add further elements, they look like this:

<input <b>id="i-name$xforms-input-1·2" ... />
<input <b>id="i-name$xforms-input-1·3" ... />

There is no longer attribute maxlength and a different format of id (name·1$xforms-input-1 and name$xforms-input-1·2).

Why maxlenght attribute is not included and why id formats are different? Why is this happening? I write the counter of characters, which uses both attributes.

macikacz wrote

In element repeat I have input:

<xf:repeat id="rid" nodeset="instance('persons')/sl:person" appearance="full">
   <xf:input id="i-name" ref="sl:name" <b>xxf:maxlength="320">
   </xf:input>
</xf:repeat>

and triger:

<xf:trigger>
        <xf:label ref="..."/>       
        <xf:action ev:event="DOMActivate">
                <xf:insert bind="b-person" at="index('rid')" position="after" origin="instance('persons-temp')/sl:person" ev:event="DOMActivate"/>
        </xf:action>
</xf:trigger>

At the beginning, first element in the html looks like this:

<input <b>id="i-name·1$xforms-input-1" ... maxlength="320" />

When I add further elements, they look like this:

<input <b>id="i-name$xforms-input-1·2" ... />
<input <b>id="i-name$xforms-input-1·3" ... />

There is no longer attribute maxlength and a different format of id (name·1$xforms-input-1 and name$xforms-input-1·2).

Why maxlenght attribute is not included and why id formats are different? Why is this happening? I write the counter of characters, which uses both attributes.

I tried to reproduce this by creating a test case, but didn't experiment any of the issues you mentioned above (different ID, and maxlength missing from added iterations). My test case: http://pastie.org/590687. If you still have this problem, could you submit a simple/minimal test case that run in the XForms sandbox and shows this issue?

Alex

Alessandro Vernet wrote

I tried to reproduce this by creating a test case, but didn't experiment any of the issues you mentioned above (different ID, and maxlength missing from added iterations). My test case: http://pastie.org/590687. If you still have this problem, could you submit a simple/minimal test case that run in the XForms sandbox and shows this issue?

Alex

I put orbeon-resources-public.jar from Nightly Build and now atribute maxlength is ok. ID is still in the wrong format, but this is not a problem. When I connected the Nightly Build version, some of the forms was not complete. Forms were written for Orbeon 3.6 and probably this is the reason - some elements or attributes are handled differently.

Thank you for your help.

Alessandro Vernet wrote

macikacz wrote

In element repeat I have input:

<xf:repeat id="rid" nodeset="instance('persons')/sl:person" appearance="full">
   <xf:input id="i-name" ref="sl:name" <b>xxf:maxlength="320">
   </xf:input>
</xf:repeat>

and triger:

<xf:trigger>
        <xf:label ref="..."/>       
        <xf:action ev:event="DOMActivate">
                <xf:insert bind="b-person" at="index('rid')" position="after" origin="instance('persons-temp')/sl:person" ev:event="DOMActivate"/>
        </xf:action>
</xf:trigger>

At the beginning, first element in the html looks like this:

<input <b>id="i-name·1$xforms-input-1" ... maxlength="320" />

When I add further elements, they look like this:

<input <b>id="i-name$xforms-input-1·2" ... />
<input <b>id="i-name$xforms-input-1·3" ... />

There is no longer attribute maxlength and a different format of id (name·1$xforms-input-1 and name$xforms-input-1·2).

Why maxlenght attribute is not included and why id formats are different? Why is this happening? I write the counter of characters, which uses both attributes.

I tried to reproduce this by creating a test case, but didn't experiment any of the issues you mentioned above (different ID, and maxlength missing from added iterations). My test case: http://pastie.org/590687. If you still have this problem, could you submit a simple/minimal test case that run in the XForms sandbox and shows this issue?

Alex

I found bug. Elements that are generated on the server side have id in format name·1$xforms-input-1. Elements that are generated on client side have id in format name$xforms-input-1·1. Am I right?

macikacz wrote

I found bug. Elements that are generated on the server side have id in format name·1$xforms-input-1. Elements that are generated on client side have id in format name$xforms-input-1·1. Am I right?

Yes, good catch. I added a bug for this, and we'll be fixing this one soon:

http://forge.ow2.org/tracker/index.php?func=detail&aid=314169&group_id=168&atid=350207

Alex

This bug is now fixed in git.

-Erik

Alessandro Vernet wrote

macikacz wrote

I found bug. Elements that are generated on the server side have id in format name·1$xforms-input-1. Elements that are generated on client side have id in format name$xforms-input-1·1. Am I right?

Yes, good catch. I added a bug for this, and we'll be fixing this one soon:

http://forge.ow2.org/tracker/index.php?func=detail&aid=314169&group_id=168&atid=350207

Alex