Orbeon Forms community mailing list

Inexplicable results with repeatable fr:autocomplete and xforms:delete

Classic

List

Threaded

13 messages Options

Ethan Gruber

Inexplicable results with repeatable fr:autocomplete and xforms:delete

I've looked through nabble and have not found this issue (bug?) addressed specifically.

I have a trigger that inserts a repeatable input. The input uses fr:autocomplete to provide a list of suggests that are defined in the model (from Solr facets).

Here's the trigger:

<xforms:trigger appearance="minimal">
        <xforms:label>
            <img src="/apps/ead/images/add.gif"/>Subject</xforms:label>
        <xforms:insert ev:event="DOMActivate" context="." nodeset="./child::node()[last()]"
            origin="instance('subject-template')"/>
    </xforms:trigger>

Here's the input:

<xforms:repeat nodeset="subject">
        <div style="margin-bottom:10px">
            
            <fr:autocomplete ref="." dynamic-itemset="false" style="float: left;">
                <xforms:label>Subject</xforms:label>
                <xforms:itemset nodeset="instance('subjects-template')//lst[@name='subject']/int">
                    <xforms:label ref="@name"/>
                    <xforms:value ref="@name"/>
                </xforms:itemset>
            </fr:autocomplete>

            <xforms:trigger appearance="minimal">
                <xforms:delete ev:event="DOMActivate" nodeset="."/>
                <xforms:label>
                    <img src="/apps/ead/images/remove.gif"/>
                </xforms:label>
            </xforms:trigger>
        </div>
    </xforms:repeat>

Everything works fine with the trigger and the autocomplete until I delete one of the elements. After I delete one element, the next time I initialize the xforms:insert trigger, an xforms:input is inserted that has no autocomplete information. I have noticed this bug surfaces not only when I delete one of the "subjects," but also delete the parent node of "subject" and re-add its parent node. If I look at the source of a working autocomplete input and an input inserted after a deletion in Firebug (for Firefox), there is an interesting difference. Everything is identical down to the <div style="float:left">

HTML of input where autocomplete works:

<div class="yui-ac" style="float: left;">

</span>

<div class="yui-ac-content" style="display: none;">
...autocomplete info: <ul>, etc....

</div>

</div>

HTML of input where autocomplete does not work, inserted after an xforms:delete is performed on a subject:

<div style="float: left;">

</span>

</div>

You can see some differences here. The top level div on the non-working input lacks the class "yui-ac." The <input> lacks a class "yui-ac-input" and autocomplete="off". The div which is supposed to contain the suggested options lacks the class "yui-ac-container" and contains no descendant content.

Any ideas? Having an autosuggest functionality on repeatable elements is very important in my project, and it is equally important to be able to delete those elements and add more fluidly.

Any help is greatly appreciated.

Thank you,
Ethan Gruber

--
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

Erik Bruchez-3

Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

Ethan,

Is this issue still current?

-Erik

On Tue, Dec 1, 2009 at 9:03 AM, Ethan Gruber <[hidden email]> wrote:

> I've looked through nabble and have not found this issue (bug?) addressed
> specifically.
>
> I have a trigger that inserts a repeatable input. The input uses
> fr:autocomplete to provide a list of suggests that are defined in the model
> (from Solr facets).
>
> Here's the trigger:
>
> <xforms:trigger appearance="minimal">
>         <xforms:label>
>             <img src="/apps/ead/images/add.gif"/>Subject</xforms:label>
>         <xforms:insert ev:event="DOMActivate" context="."
> nodeset="./child::node()[last()]"
>             origin="instance('subject-template')"/>
>     </xforms:trigger>
>
> Here's the input:
>
> <xforms:repeat nodeset="subject">
>         <div style="margin-bottom:10px">
>             
>             <fr:autocomplete ref="." dynamic-itemset="false" style="float:
> left;">
>                 <xforms:label>Subject</xforms:label>
>                 <xforms:itemset
> nodeset="instance('subjects-template')//lst[@name='subject']/int">
>                     <xforms:label ref="@name"/>
>                     <xforms:value ref="@name"/>
>                 </xforms:itemset>
>             </fr:autocomplete>
>
>             <xforms:trigger appearance="minimal">
>                 <xforms:delete ev:event="DOMActivate" nodeset="."/>
>                 <xforms:label>
>                     <img src="/apps/ead/images/remove.gif"/>
>                 </xforms:label>
>             </xforms:trigger>
>         </div>
>     </xforms:repeat>
>
>
> Everything works fine with the trigger and the autocomplete until I delete
> one of the elements. After I delete one element, the next time I initialize
> the xforms:insert trigger, an xforms:input is inserted that has no
> autocomplete information. I have noticed this bug surfaces not only when I
> delete one of the "subjects," but also delete the parent node of "subject"
> and re-add its parent node. If I look at the source of a working
> autocomplete input and an input inserted after a deletion in Firebug (for
> Firefox), there is an interesting difference. Everything is identical down
> to the <div style="float:left">
>
> HTML of input where autocomplete works:
>
> <div class="yui-ac" style="float: left;">
> <span id="xf-2866$input·1-1" class="fr-autocomplete-input xforms-control
> xforms-input xforms-visited">
>     <input id="xf-2866$input$xforms-input-1·1-1" class="xforms-input-input
> yui-ac-input" type="text" value="" name="xf-2866$input$xforms-input-1·1-1" autocomplete="off"/>
> </span>
> <div id="yui-gen5" class="fr-autocomplete-yui-div yui-ac-container">
>     <div class="yui-ac-content" style="display: none;">
>       ...autocomplete info: <ul>, etc....
>     </div>
> </div>
> </div>
>
> HTML of input where autocomplete does not work, inserted after an
> xforms:delete is performed on a subject:
>
> <div style="float: left;">
> <span id="xf-2866$input·1-2" class="fr-autocomplete-input xforms-control
> xforms-input xforms-visited">
>
> <input id="xf-2866$input$xforms-input-1·1-2" class="xforms-input-input" type="text" value="" name="xf-2866$input$xforms-input-1·1-2"/>
> </span>
> <div class="fr-autocomplete-yui-div"/>
> </div>
>
> You can see some differences here. The top level div on the non-working
> input lacks the class "yui-ac." The <input> lacks a class "yui-ac-input"
> and autocomplete="off". The div which is supposed to contain the suggested
> options lacks the class "yui-ac-container" and contains no descendant
> content.
>
> Any ideas? Having an autosuggest functionality on repeatable elements is
> very important in my project, and it is equally important to be able to
> delete those elements and add more fluidly.
>
> Any help is greatly appreciated.
>
> Thank you,
> Ethan Gruber
>
>
>
>
>
> --
> 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
>
>

Ethan Gruber

Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

Hi Erik,

I just tested this on a nightly build from last Friday and the autocomplete is now working in repeat as one might expect after deleting an entry. Excellent!

Ethan

On Mon, Feb 15, 2010 at 9:50 PM, Erik Bruchez <[hidden email]> wrote:

Ethan,

Is this issue still current?

-Erik

On Tue, Dec 1, 2009 at 9:03 AM, Ethan Gruber <[hidden email]> wrote:
> I've looked through nabble and have not found this issue (bug?) addressed
> specifically.
>
> I have a trigger that inserts a repeatable input. The input uses
> fr:autocomplete to provide a list of suggests that are defined in the model
> (from Solr facets).
>
> Here's the trigger:
>
> <xforms:trigger appearance="minimal">
>         <xforms:label>
>             <img src="/apps/ead/images/add.gif"/>Subject</xforms:label>
>         <xforms:insert ev:event="DOMActivate" context="."
> nodeset="./child::node()[last()]"
>             origin="instance('subject-template')"/>
>     </xforms:trigger>
>
> Here's the input:
>
> <xforms:repeat nodeset="subject">
>         <div style="margin-bottom:10px">
>             
>             <fr:autocomplete ref="." dynamic-itemset="false" style="float:
> left;">
>                 <xforms:label>Subject</xforms:label>
>                 <xforms:itemset
> nodeset="instance('subjects-template')//lst[@name='subject']/int">
>                     <xforms:label ref="@name"/>
>                     <xforms:value ref="@name"/>
>                 </xforms:itemset>
>             </fr:autocomplete>
>
>             <xforms:trigger appearance="minimal">
>                 <xforms:delete ev:event="DOMActivate" nodeset="."/>
>                 <xforms:label>
>                     <img src="/apps/ead/images/remove.gif"/>
>                 </xforms:label>
>             </xforms:trigger>
>         </div>
>     </xforms:repeat>
>
>
> Everything works fine with the trigger and the autocomplete until I delete
> one of the elements. After I delete one element, the next time I initialize
> the xforms:insert trigger, an xforms:input is inserted that has no
> autocomplete information. I have noticed this bug surfaces not only when I
> delete one of the "subjects," but also delete the parent node of "subject"
> and re-add its parent node. If I look at the source of a working
> autocomplete input and an input inserted after a deletion in Firebug (for
> Firefox), there is an interesting difference. Everything is identical down
> to the <div style="float:left">
>
> HTML of input where autocomplete works:
>
> <div class="yui-ac" style="float: left;">
> <span id="xf-2866$input·1-1" class="fr-autocomplete-input xforms-control
> xforms-input xforms-visited">
>     <input id="xf-2866$input$xforms-input-1·1-1" class="xforms-input-input
> yui-ac-input" type="text" value="" name="xf-2866$input$xforms-input-1·1-1" autocomplete="off"/>
> </span>
> <div id="yui-gen5" class="fr-autocomplete-yui-div yui-ac-container">
>     <div class="yui-ac-content" style="display: none;">
>       ...autocomplete info: <ul>, etc....
>     </div>
> </div>
> </div>
>
> HTML of input where autocomplete does not work, inserted after an
> xforms:delete is performed on a subject:
>
> <div style="float: left;">
> <span id="xf-2866$input·1-2" class="fr-autocomplete-input xforms-control
> xforms-input xforms-visited">
>
> <input id="xf-2866$input$xforms-input-1·1-2" class="xforms-input-input" type="text" value="" name="xf-2866$input$xforms-input-1·1-2"/>
> </span>
> <div class="fr-autocomplete-yui-div"/>
> </div>
>
> You can see some differences here. The top level div on the non-working
> input lacks the class "yui-ac." The <input> lacks a class "yui-ac-input"
> and autocomplete="off". The div which is supposed to contain the suggested
> options lacks the class "yui-ac-container" and contains no descendant
> content.
>
> Any ideas? Having an autosuggest functionality on repeatable elements is
> very important in my project, and it is equally important to be able to
> delete those elements and add more fluidly.
>
> Any help is greatly appreciated.
>
> Thank you,
> Ethan Gruber
>
>
>
>
>

> --
> 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
>
>

--
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

Erik Bruchez-3

Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

Great!

-Erik

On Fri, Feb 19, 2010 at 7:54 AM, Ethan Gruber <[hidden email]> wrote:

> Hi Erik,
>
> I just tested this on a nightly build from last Friday and the autocomplete
> is now working in repeat as one might expect after deleting an entry.
> Excellent!
>
> Ethan
>
> On Mon, Feb 15, 2010 at 9:50 PM, Erik Bruchez <[hidden email]> wrote:
>>
>> Ethan,
>>
>> Is this issue still current?
>>
>> -Erik
>>
>> On Tue, Dec 1, 2009 at 9:03 AM, Ethan Gruber <[hidden email]> wrote:
>> > I've looked through nabble and have not found this issue (bug?)
>> > addressed
>> > specifically.
>> >
>> > I have a trigger that inserts a repeatable input. The input uses
>> > fr:autocomplete to provide a list of suggests that are defined in the
>> > model
>> > (from Solr facets).
>> >
>> > Here's the trigger:
>> >
>> > <xforms:trigger appearance="minimal">
>> >         <xforms:label>
>> >             <img src="/apps/ead/images/add.gif"/>Subject</xforms:label>
>> >         <xforms:insert ev:event="DOMActivate" context="."
>> > nodeset="./child::node()[last()]"
>> >             origin="instance('subject-template')"/>
>> >     </xforms:trigger>
>> >
>> > Here's the input:
>> >
>> > <xforms:repeat nodeset="subject">
>> >         <div style="margin-bottom:10px">
>> >             
>> >             <fr:autocomplete ref="." dynamic-itemset="false"
>> > style="float:
>> > left;">
>> >                 <xforms:label>Subject</xforms:label>
>> >                 <xforms:itemset
>> > nodeset="instance('subjects-template')//lst[@name='subject']/int">
>> >                     <xforms:label ref="@name"/>
>> >                     <xforms:value ref="@name"/>
>> >                 </xforms:itemset>
>> >             </fr:autocomplete>
>> >
>> >             <xforms:trigger appearance="minimal">
>> >                 <xforms:delete ev:event="DOMActivate" nodeset="."/>
>> >                 <xforms:label>
>> >                     <img src="/apps/ead/images/remove.gif"/>
>> >                 </xforms:label>
>> >             </xforms:trigger>
>> >         </div>
>> >     </xforms:repeat>
>> >
>> >
>> > Everything works fine with the trigger and the autocomplete until I
>> > delete
>> > one of the elements. After I delete one element, the next time I
>> > initialize
>> > the xforms:insert trigger, an xforms:input is inserted that has no
>> > autocomplete information. I have noticed this bug surfaces not only
>> > when I
>> > delete one of the "subjects," but also delete the parent node of
>> > "subject"
>> > and re-add its parent node. If I look at the source of a working
>> > autocomplete input and an input inserted after a deletion in Firebug
>> > (for
>> > Firefox), there is an interesting difference. Everything is identical
>> > down
>> > to the <div style="float:left">
>> >
>> > HTML of input where autocomplete works:
>> >
>> > <div class="yui-ac" style="float: left;">
>> > <span id="xf-2866$input·1-1" class="fr-autocomplete-input
>> > xforms-control
>> > xforms-input xforms-visited">
>> >
>> > <input id="xf-2866$input$xforms-input-1·1-1" class="xforms-input-input
>> >
>> > yui-ac-input" type="text" value="" name="xf-2866$input$xforms-input-1·1-1" autocomplete="off"/>
>> > </span>
>> > <div id="yui-gen5" class="fr-autocomplete-yui-div yui-ac-container">
>> >     <div class="yui-ac-content" style="display: none;">
>> >       ...autocomplete info: <ul>, etc....
>> >     </div>
>> > </div>
>> > </div>
>> >
>> > HTML of input where autocomplete does not work, inserted after an
>> > xforms:delete is performed on a subject:
>> >
>> > <div style="float: left;">
>> > <span id="xf-2866$input·1-2" class="fr-autocomplete-input
>> > xforms-control
>> > xforms-input xforms-visited">
>> >
>> >
>> > <input id="xf-2866$input$xforms-input-1·1-2" class="xforms-input-input" type="text" value="" name="xf-2866$input$xforms-input-1·1-2"/>
>> > </span>
>> > <div class="fr-autocomplete-yui-div"/>
>> > </div>
>> >
>> > You can see some differences here. The top level div on the non-working
>> > input lacks the class "yui-ac." The <input> lacks a class
>> > "yui-ac-input"
>> > and autocomplete="off". The div which is supposed to contain the
>> > suggested
>> > options lacks the class "yui-ac-container" and contains no descendant
>> > content.
>> >
>> > Any ideas? Having an autosuggest functionality on repeatable elements
>> > is
>> > very important in my project, and it is equally important to be able to
>> > delete those elements and add more fluidly.
>> >
>> > Any help is greatly appreciated.
>> >
>> > Thank you,
>> > Ethan Gruber
>> >
>> >
>> >
>> >
>> >
>> > --
>> > 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
>> >
>> >
>>
>>
>> --
>> 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
>>
>
>
>
> --
> 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
>
>

jesintha_p

Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

HI Ethan,

I recently upgraded to Orbeon 3.9 and modified the orbeon filter jar and changed my select box to autocomplete.

The issue is reproducible for me.

Can you please let me know if i missed out on something

Thanks,
Jesi

jesintha_p

Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

In reply to this post by Erik Bruchez-3

Ethan Gruber

Re: Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

Hi Jesi,

It's difficult to say. Are you having problems deleting a repeatable
fr:autocomplete control? The issue is almost a year and a half old
and I have since moved to representing my control in XBL, and have not
had any problems since.

Ethan

On Thu, May 26, 2011 at 11:12 AM, jesintha_p
<[hidden email]> wrote:

> HI Ethan,
>
> I recently upgraded to Orbeon 3.9 and modified the orbeon filter jar and
> changed my select box to autocomplete.
>
> The issue is reproducible for me.
>
> Can you please let me know if i missed out on something
>
> Thanks,
> Jesi
>
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Inexplicable-results-with-repeatable-fr-autocomplete-and-xforms-delete-tp932322p3552801.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>
>
> --
> 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
>
>

jesintha_p

Re: Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

Yes Ethan, the autocomplete box inside repeat is not functioning as expected. If we have more than one items only the first one works correctly, the new one dont get the values for the autocomplete, the first one only has those divs, the others get only one empty div

jesintha_p

Re: Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

In reply to this post by Ethan Gruber

Ethan Gruber

Re: Re: Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

In reply to this post by jesintha_p

I recall having this problem and had to make the control use an itemset based on its current position. For each repeatable element to which the fr:autocomplete is assigned, I had to insert a element to hold the response from the dynamic itemset query whose position is identical to that of the fr:autocomplete within its context into an aggregated instance. For example, the third fr:autocomplete within your repeatable element had to refer to instance('suggestions-aggregate-subject')/response[3]. See http://code.google.com/p/eaditor/source/browse/trunk/inputs/subject-autocomplete.xml?r=110 for more info. The $uid variable is tied to the position and 'suggestions-aggregate-subject' is the aggregate instance. If you deleted your third fr:autocomplete control, you also had to remove instance('suggestions-aggregate-subject')/response[3].

This ceased to be an issue when I migrated to XBL as each fr:autocomplete relied upon its own internal model.

Ethan

On Fri, May 27, 2011 at 2:09 AM, jesintha_p <[hidden email]> wrote:

Yes Ethan, the autocomplete box inside repeat is not functioning as expected.
If we have more than one items only the first one works correctly, the new
one dont get the values for the autocomplete, the first one only has those
divs, the others get only one empty div

--

View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Inexplicable-results-with-repeatable-fr-autocomplete-and-xforms-delete-tp932322p3554457.html

Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.

--
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

Alessandro Vernet

Re: Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

Administrator

In reply to this post by jesintha_p

Hi Jesi,

Could you create a minimal stand-alone XForms example we can use to reproduce the issue you're having with the autocomplete in repeats?

Alex

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

jesintha_p

Re: Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

Hi Alex,

we found that when we add a new element in repeat, if we add it at the top , there bottom auto-complete boxes doesnt show any values however if we add them in the bottom , it works as expected.

Thanks,
Jesi

Alessandro Vernet

Re: Re: Re: Re: Inexplicable results with repeatable fr:autocomplete and xforms:delete

Administrator

Hi Jesi,

This is rather strange, but I guess it will do since you seem to have a workaround.

Alex

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet