Some may recall, I have had big
problems with a simple submission a month or so... well it took me
about a month (ok i did do other things ;)) to figure this out! I found
it while I was looking in the mailing list for another problem.
This topic figured it out for me : http://www.nabble.com/autocompletion-bug-tf4308727.html#a12266021 In my submission, it would work under Safari, Opera and Internet Explorer but not under Firefox! What really drove me nuts is that some rare times, it would work with Firefox too! The secret is the autocomplete Firefox does for forms, as stupid as this! Apparently, the instance is not correctly updated when one uses what Firefox suggests! Here is an example. As a username, I put "Steph", but I write every letter, one by one. My submission will work fine. Let's start over and just write the frist letter "s", Firefox will then suggestion "Steph" because it saved it from previous input. But if I select what Firefox suggests, my instance will only have the letter s !!!!! And that's why it wouldn't work! Alex wrote : " Even if I can't reproduce this, the reason it doesn't work is that we are listening on a "keyup" event, and Firefox does not send that event when you select something from the list. Instead Firefox sends an "input" event, which is new to me ". Now apparently this bug (August) still exist in Orbeon. So my next goal was to disactivate this autocompletion. In HTML, one would put : autocomplete="off". So I did the same in my xform but that wouldn't work. In the final source page, I wouldn't see the attribute autocomplete. This is the line where I would like to have my attribute autocomplete : <input type="text" class="xforms-input-input" value="" name="xforms-element-6" id="input-xforms-element-6"/> I tried with some javascript to getElementById('input-xforms-element-6') and set an attribute to autocomplete to off, but that wouldn't work. Can someone help me ? I don't want to disactivate this property of Firefox because their will be many users... I have to find out how to put this attribute in that input! Thanks! -- 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 |
Administrator
|
Stephane,
Try using xxforms:autocomplete="off" on xforms:input. I believe that the original issue related to xforms:input with appearance="xxforms:autocomplete" and selection="open". Is that what you are getting, or is this a separate problem? -Erik On Nov 25, 2007, at 3:15 AM, Stephane Ruchet wrote: > Some may recall, I have had big problems with a simple submission a > month or so... well it took me about a month (ok i did do other > things ;)) to figure this out! I found it while I was looking in the > mailing list for another problem. > > This topic figured it out for me : http://www.nabble.com/autocompletion-bug-tf4308727.html#a12266021 > > In my submission, it would work under Safari, Opera and Internet > Explorer but not under Firefox! What really drove me nuts is that > some rare times, it would work with Firefox too! > > The secret is the autocomplete Firefox does for forms, as stupid as > this! Apparently, the instance is not correctly updated when one > uses what Firefox suggests! Here is an example. As a username, I put > "Steph", but I write every letter, one by one. My submission will > work fine. Let's start over and just write the frist letter "s", > Firefox will then suggestion "Steph" because it saved it from > previous input. But if I select what Firefox suggests, my instance > will only have the letter s !!!!! And that's why it wouldn't work! > > Alex wrote : " Even if I can't reproduce this, the reason it doesn't > work is that we are listening on a "keyup" event, and Firefox does > not send that event when you select something from the list. Instead > Firefox sends an "input" event, which is new to me ". > > Now apparently this bug (August) still exist in Orbeon. So my next > goal was to disactivate this autocompletion. In HTML, one would > put : autocomplete="off". So I did the same in my xform but that > wouldn't work. In the final source page, I wouldn't see the > attribute autocomplete. > > This is the line where I would like to have my attribute > autocomplete : > > <input type="text" class="xforms-input-input" value="" name="xforms- > element-6" id="input-xforms-element-6"/> > > I tried with some javascript to getElementById('input-xforms- > element-6') and set an attribute to autocomplete to off, but that > wouldn't work. > > Can someone help me ? I don't want to disactivate this property of > Firefox because their will be many users... I have to find out how > to put this attribute in that input! Thanks! > > > -- > 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 Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.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 |
Hi Erik,
Yes this was what I was looking for. Now Firefox doesn't propose anything when one enters the first letters of a word. Maybe I didn't express myself correctly : this has nothing to do with appearance="xxforms:autocomplete" because I don't use it. In any form on the web, when you enter your first name, Erik, the first time you will have to write the four letters. But if you have to enter it another time, on another page, 5 days later, when you will enter the letter "E", Firefox will propose the word Erik to gain you some time! Well if you use this feature, the instance is not updated, and for me, it's clearly a bug of OPS. It would be nice if it was corrected because I believe it isn't to difficult (after what Alex said). Steph Erik Bruchez a écrit : Stephane, -- 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 |
Hi,
I just wanted to add, that it sometimes could be very useful to be able to use Firefox's auto-complete. And for us, there have been numerous issues, when user enters his username and password (actually selects username from Firefox's suggestions) and our Orbeon based system responds with - "incorrect username!" just because of this bug (referenced instance element is empty). And we have to tell our users to turn off Firefox's auto-complete in Tools > Options > Privacy > Remember what I type in forms and search bar, that's because we know the cause. I wanted to create a repeatable example of this, but I could not find how to make Firefox consistently suggest entered values. We believe it looks for a consistent ID attribute on the input control. Jurgis Stephane Ruchet wrote: Hi Erik, -- Jurģis Lukss SIA "Mikrokods" mob. 26458439 -- 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 |
Use xxforms:autocomplete="off" so that Firefox doesn't propose anything! At least you won't have any problem... while they fix this problem. Jurģis Lukss a écrit : Hi, -- 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 |
In reply to this post by StephR
I've seen the same thing. The problem is that Firefox isn't sending change events when a user selects an option from autocomplete. (This is Firefox's own autocomplete, not the one from Orbeon)
I've looked into this myself, but it doesn't seem like Firefox sends any consistent event. Autocomplete could be triggered either by clicking on the option, or by arrowing down and hitting enter. I'm not too familiar with the underlying javascript that powers the forms, but would it be possible to compare the contents of the input field and the contents of the bound node and update the node if they don't match? You would probably only want to do this on blur if incremental is turned off. I don't know what you would have to do with it on other than perform the check on every keypress or click. (possibly expensive, I think) I haven't been able to test it because my hard drive recently died and I'm running off a Live CD, but I think this problem might also exist if some other method (such as an extension or another js function) writes to the contents of the input field. Hope this helps track down this problem. I would really like to see this one fixed. Daniel E. Renfer http://kronkltd.net/ On 11/27/07,
Stephane Ruchet <[hidden email]> wrote:
-- 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 |
Administrator
|
Thanks for looking into this.
I could have sworn that we had a bug entered for this, but apparently not. I just created one: http://forge.objectweb.org/tracker/index.php?func=detail&aid=307929&group_id=168&atid=350207 -Erik On Nov 27, 2007, at 4:51 AM, Daniel Renfer wrote: > I've seen the same thing. The problem is that Firefox isn't sending > change events when a user selects an option from autocomplete. (This > is Firefox's own autocomplete, not the one from Orbeon) > > I've looked into this myself, but it doesn't seem like Firefox sends > any consistent event. Autocomplete could be triggered either by > clicking on the option, or by arrowing down and hitting enter. > > I'm not too familiar with the underlying javascript that powers the > forms, but would it be possible to compare the contents of the input > field and the contents of the bound node and update the node if they > don't match? You would probably only want to do this on blur if > incremental is turned off. I don't know what you would have to do > with it on other than perform the check on every keypress or click. > (possibly expensive, I think) > > I haven't been able to test it because my hard drive recently died > and I'm running off a Live CD, but I think this problem might also > exist if some other method (such as an extension or another js > function) writes to the contents of the input field. > > Hope this helps track down this problem. I would really like to see > this one fixed. > > Daniel E. Renfer > http://kronkltd.net/ > > On 11/27/07, Stephane Ruchet <[hidden email]> wrote: > Hi Erik, > > Yes this was what I was looking for. Now Firefox doesn't propose > anything when one enters the first letters of a word. Maybe I didn't > express myself correctly : this has nothing to do with > appearance="xxforms:autocomplete" because I don't use it. > > In any form on the web, when you enter your first name, Erik, the > first time you will have to write the four letters. But if you have > to enter it another time, on another page, 5 days later, when you > will enter the letter "E", Firefox will propose the word Erik to > gain you some time! Well if you use this feature, the instance is > not updated, and for me, it's clearly a bug of OPS. It would be nice > if it was corrected because I believe it isn't to difficult (after > what Alex said). > > Steph > > Erik Bruchez a écrit : >> Stephane, >> >> Try using xxforms:autocomplete="off" on xforms:input. >> >> I believe that the original issue related to xforms:input with >> appearance="xxforms:autocomplete" and selection="open". Is that >> what you are getting, or is this a separate problem? >> >> -Erik >> >> On Nov 25, 2007, at 3:15 AM, Stephane Ruchet wrote: >> >>> Some may recall, I have had big problems with a simple submission >>> a month or so... well it took me about a month (ok i did do other >>> things ;)) to figure this out! I found it while I was looking in >>> the mailing list for another problem. >>> >>> This topic figured it out for me : http://www.nabble.com/autocompletion-bug-tf4308727.html#a12266021 >>> >>> In my submission, it would work under Safari, Opera and Internet >>> Explorer but not under Firefox! What really drove me nuts is that >>> some rare times, it would work with Firefox too! >>> >>> The secret is the autocomplete Firefox does for forms, as stupid >>> as this! Apparently, the instance is not correctly updated when >>> one uses what Firefox suggests! Here is an example. As a username, >>> I put "Steph", but I write every letter, one by one. My submission >>> will work fine. Let's start over and just write the frist letter >>> "s", Firefox will then suggestion "Steph" because it saved it from >>> previous input. But if I select what Firefox suggests, my instance >>> will only have the letter s !!!!! And that's why it wouldn't work! >>> >>> Alex wrote : " Even if I can't reproduce this, the reason it >>> doesn't work is that we are listening on a "keyup" event, and >>> Firefox does not send that event when you select something from >>> the list. Instead Firefox sends an "input" event, which is new to >>> me ". >>> >>> Now apparently this bug (August) still exist in Orbeon. So my next >>> goal was to disactivate this autocompletion. In HTML, one would >>> put : autocomplete="off". So I did the same in my xform but that >>> wouldn't work. In the final source page, I wouldn't see the >>> attribute autocomplete. >>> >>> This is the line where I would like to have my attribute >>> autocomplete : >>> >>> <input type="text" class="xforms-input-input" value="" >>> name="xforms-element-6" id="input-xforms-element-6"/> >>> >>> I tried with some javascript to getElementById('input-xforms- >>> element-6') and set an attribute to autocomplete to off, but that >>> wouldn't work. >>> >>> Can someone help me ? I don't want to disactivate this property of >>> Firefox because their will be many users... I have to find out how >>> to put this attribute in that input! Thanks! >>> >>> >>> -- >>> 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 >> >> -- >> Orbeon Forms - Web Forms for the Enterprise Done the Right Way >> http://www.orbeon.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 > > > > -- > 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 Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.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 |
Free forum by Nabble | Edit this page |