Problems with chrome autocomplete

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Problems with chrome autocomplete

andi22
This post was updated on .
Hi,

While I was testing my form, It appeared me this issue:



It appeared when I select an option of the autocomplete (one that I entered testing before), then I clear the autofill with the clear form option that google chrome lets.



Then the window appear and couldn't do anything else.


(Both messages appear)

My question is the next one:

¿There is any option to disable in all the form the option autocomplete? I tried to put in every element the autocomplete="off", like this:

 <xforms:bind id="codigoPostal-bind" nodeset="codigoPostal" name="codigoPostal"
                                 autocomplete="off"
                                 type="xs:string"
                                 required="true()"
                                 relevant="if ($pais=&#34;108&#34;) then true() else false()"/>

but i'm still able to autocomplete.

¿Could be another option or solution for this problem?

Thanks for your time

Andres
Reply | Threaded
Open this post in threaded view
|

Re: Problems with chrome autocomplete

Erik Bruchez
Administrator
That seems like a bug with an older version of Orbeon Forms (3.9?).

I am not sure if stopping the browser from autocompleting will work, but if somehow you managed to get <form autocomplete="off" ...> on the form element produced by Orbeon Forms, that might do the trick.

-Erik
Reply | Threaded
Open this post in threaded view
|

Re: Problems with chrome autocomplete

andi22
Hi Erik.

I've tried to put the <form: autocomplete="off"> but hadn't work. There is any other solution? Or is it a bug? I have the version 3.9.1.
The problem just appeares in chrome when I click the clear form option.

Thanks for your time

Andres
Reply | Threaded
Open this post in threaded view
|

Re: Problems with chrome autocomplete

Erik Bruchez
Administrator
Andres,

Yes I woulds say it's a bug with 3.9.1. I don't think it happens with 4.x.

-Erik