I have mootools form validation installed on a simple form, and it works perfectly on IE7, FF2, Safari 3 for Win, but it fails almost constantly on Opera 9.26.
Most of the time on Opera 9.26 I can click in and out of various required or otherwise validated fields and it doesn't do anything--as if the script is not loaded or not working. However, occassionally, it will start to validate and give the proper messages if I play around in the fields enough (or in a certain order?).
I tried the prototype validation toolkit and it behaves the same on Opera 9.26 as well--it doesn't work for me. I have not tried the prototype js validation toolkit on the other browsers because they are not causing me a problem and I prefer mootools because it is a smaller sized script.
Can anyone else confirm this is a problem for them as well?
Thanks,
Johnny
Most of the time on Opera 9.26 I can click in and out of various required or otherwise validated fields and it doesn't do anything--as if the script is not loaded or not working. However, occassionally, it will start to validate and give the proper messages if I play around in the fields enough (or in a certain order?).
I tried the prototype validation toolkit and it behaves the same on Opera 9.26 as well--it doesn't work for me. I have not tried the prototype js validation toolkit on the other browsers because they are not causing me a problem and I prefer mootools because it is a smaller sized script.
Can anyone else confirm this is a problem for them as well?
Thanks,
Johnny
hmmm. just discovered it validated on one of my forms in Opera, but not another. Will investigate more tomorrow.
j
j
OK, I found the cause.
Hopefully this information will prevent anyone else the headaches it caused me to try and figure it out.
I created my chrono form in an article using the {chronocontact}form_name{/chronocontact} format.
My editor in Joomla 1.5 is TinyMCE and in one of my articles where I had a form, it had wrapped the chronocontact call in <p> tags so the html looked like this:
<p>{chronocontact}form_name{/chronocontact}</p>
This caused XHTML transitional validation errors because the Chronform contains the mandatory lines:
<div class="chronoform">
<a href="http://www.chronoengine.com">Joomla Professional Work</a></div>
which exist unless you buy a license.
The XHTML validation errors are thus caused by having a block element (div) inside a line element (p). This XHTML validation error actually breaks the JS Mootools and Prototype form validation code in Opera, even though it does not break it on any other browser.
So, moral of the story, make sure your call to the chronoform is not wrapped in a line tag and all should be well!
Johnny
Hopefully this information will prevent anyone else the headaches it caused me to try and figure it out.
I created my chrono form in an article using the {chronocontact}form_name{/chronocontact} format.
My editor in Joomla 1.5 is TinyMCE and in one of my articles where I had a form, it had wrapped the chronocontact call in <p> tags so the html looked like this:
<p>{chronocontact}form_name{/chronocontact}</p>
This caused XHTML transitional validation errors because the Chronform contains the mandatory lines:
<div class="chronoform">
<a href="http://www.chronoengine.com">Joomla Professional Work</a></div>
which exist unless you buy a license.
The XHTML validation errors are thus caused by having a block element (div) inside a line element (p). This XHTML validation error actually breaks the JS Mootools and Prototype form validation code in Opera, even though it does not break it on any other browser.
So, moral of the story, make sure your call to the chronoform is not wrapped in a line tag and all should be well!
Johnny
Thanks Johnny!!
This topic is locked and no more replies can be posted.
