PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

HTML5 Validation with for attribute not correct

  1. I am unable to validate a page with the form on due to an attribute not being correct:

    <li id='field_1_1' class='gfield gfield_contains_required' ><label class='gfield_label' for='input_1_1.3'>Name<span class='gfield_required'>*</span></label><div class='ginput_container'><input name='input_1' id='input_1_1' type='text' value='' class='medium' tabindex='1' /></div></li>

    The for attribute of the label element must refer to a form control.

    It looks like the for has got the .3 on the end but I have tried to remove that field and create it again but it still outputted another number on the end.

    Posted 10 years ago on Monday July 11, 2011 | Permalink
  2. Can you provide us with a link to the form so we can see the entire thing?

    Posted 10 years ago on Tuesday July 12, 2011 | Permalink
  3. Two sites:

    http://www.aap3creative.com/about-us/
    http://www.aap3.com/about_us/

    In the second by not having the css outputted it stops one error for validation but I cannot stop the for attribute problem.

    Posted 10 years ago on Wednesday July 13, 2011 | Permalink
  4. Could it be something to do with it being the widget?

    Posted 10 years ago on Friday July 15, 2011 | Permalink
  5. Sorry, I was looking into it but got a bit backed up on something else. I'll take a look at this today and let you know what I find.

    Posted 10 years ago on Friday July 15, 2011 | Permalink
  6. Thanks Kevin much appreciated :)

    Posted 10 years ago on Friday July 15, 2011 | Permalink
  7. Hi Kevin any news on this?

    Posted 10 years ago on Tuesday July 19, 2011 | Permalink
  8. Sorry, my bad here.. I got wrapped up in a few other issues and am behind a bit.

    So, the issue occurs when you're using an advanced "Name" field, but using the "simple" name format option. We've noted the discrepancy and will get that corrected for the next release.

    For now, I would suggest using just a simple single line text field to capture the name information. I tested that and it works/validates properly. The end result will be the same as the simple name option doesn't do anything advanced with the name option in regards to filtering, etc.

    Again, thanks for your patience. I'll try to step it up next time.

    Posted 10 years ago on Wednesday July 20, 2011 | Permalink
  9. Thanks Kevin sorry to have pestered you I appreciate your time and the great plugin :)

    Posted 10 years ago on Wednesday July 20, 2011 | Permalink
  10. No worries, you have been very patient and I'm very appreciative. Thanks too for helping us catch that bug.

    Posted 10 years ago on Wednesday July 20, 2011 | Permalink

This topic has been resolved and has been closed to new replies.