HTML Validator Posts Errors Coming From Forminator

  • Resolved toad78

    (@toad78)


    4 years, 8 months ago

    So I ran my site through https://validator.w3.org/ and it posted a series of errors from the form I created with Forminator (about 22). Just a few:

    Error: Bad value for attribute action on element form: Must be non-empty.
    Error: Attribute height not allowed on element textarea at this point.
    Error: CSS: min-height: Too many values or values are not recognized.
    Error: Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.)
    Error: The value of the for attribute of the label element must be the ID of a non-hidden form control.

    Now I am curious if using a ‘defer’ code could be causing this?

    • This topic was modified 4 years, 8 months ago by toad78.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @toad78

    Thank you for reporting this.

    I was able to replicate the issue, and I will report those to Forminator developers.

    I’m afraid using Defer isn’t causing those issue as I tested on my website using the default WordPress theme and no optmization feature.

    You can also bypass some warning using the Forminator > Edit the Form > Behaviour > Load form from Ajax.

    I also checked those errors, and it won’t cause any issue on your website or making the form stop from working.

    Let us know if you have any further question on this.
    Best Regards
    Patrick Freitas

    Thread Starter toad78

    (@toad78)

    So I took your suggestion and enabled the Ajax load. However, it produced slower pageloading results and Validator still posted the errors.

    Hopefully there will be a solution that will favor both issues.

    Thank you.

    Plugin Support Williams – WPMU DEV Support

    (@wpmudev-support8)

    Hi @toad78

    Thanks for response!

    As for validator, I wouldn’t really rely that much on it. It’s way out of line in many cases and can throw errors or at least warnings with quite a lot of perfectly fine sites that use modern specs/approach.

    I’m not saying that to “dismiss” the issue (as my colleague also already passed the information about that to our developers so they’d check and address it with one of future releases) but just to make it clear that those errors will not actually cause the site/plugin to break and they won’t affect e.g. search engine results’ position.

    As for the loading speed – is the page in question cached? If yes then using Ajax to load might be “breaking” cache for this particular page, thus causing it to load slower. On the other hand, it should help making sure that the form is not affected by cache (e.g. with wrong data).

    Kind regards,
    Adam

    Thread Starter toad78

    (@toad78)

    Thank you for the update. I usually DON’T rely on every ERROR that gets posted by the validator, but it is something that I thought needed to be addressed.

    BTW, yes, the page is cached.

    Hi @toad78,

    Of course, the issue is on the to-do list and will be addressed in future releases, we do appreciate bringing it to our attention ??

    As Adam mentioned previously if the page is cached then AJAX would skip that cache and can cause longer loading times, however, forms can often be affected by caching and cause wrong data to be stored, so it might be better to keep the form on a more simpler page where no-caching would have less impact.

    Cheers,
    Predrag

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘HTML Validator Posts Errors Coming From Forminator’ is closed to new replies.