Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author jazzigor

    (@jazzigor)

    This is something I haven’t been checking thoroughly enough. From what I see, the only issue https://validator.w3.org detects is a missing “scoped” attribute in the “style” tag. Please correct me if I’m wrong.

    You can circumvent that by not using Jazzy Forms’ CSS functionality at all. Uncheck the “Default CSS” option and perform styling in the theme instead.

    (Another issue arises if there are elements that without a specified ID. The validator than complains about duplicate element IDs. Avoid this one by always specifying unique IDs.)

    It seems it doesn’t take more than 5 minute to fix this, so you can expect this to be solved in the next update, scheduled for this weekend.

    Plugin Author jazzigor

    (@jazzigor)

    v0.10 should have this one solved. Please correct me if I’m wrong.

    Thread Starter energycello

    (@energycello)

    I tested it with 2 checkboxes, 1 output and 1 email button and it doesn’t validate. 5 errors

    required attribute “action” not specified
    <form class=”jzzf_form jzzf_form_1″>

    end tag for “input” omitted, but OMITTAG NO was specified

    …nput type=”checkbox” id=”jzzf_1_id1a”><label class=”jzzf_checkbox_label” for=”…

    start tag was here

    <input type=”checkbox” id=”jzzf_1_id1a”><label class=”jzzf_checkbox_label” …

    end tag for “input” omitted, but OMITTAG NO was specified

    …nput type=”checkbox” id=”jzzf_1_id2a”><label class=”jzzf_checkbox_label” for=”…

    hope it helps

    Thread Starter energycello

    (@energycello)

    start tag was here

    <input type=”checkbox” id=”jzzf_1_id2a”><label class=”jzzf_checkbox_label” …

    end tag for “input” omitted, but OMITTAG NO was specified

    …nput type=”text” readonly=”readonly” id=”jzzf_1_total” value=”Invalid formula”>

    start tag was here

    …abel” for=”jzzf_1_total”>total</label><input type=”text” readonly=”readonly” i…

    end tag for “input” omitted, but OMITTAG NO was specified

    …e=”button” class=”jzzf_email_button” id=”jzzf_1_element_3″ value=”Element (3)”>

    Thread Starter energycello

    (@energycello)

    the page is w3c validated before using the plugin, I could have done something wrong, do correct me if it is caused by me instead.

    Thread Starter energycello

    (@energycello)

    Just to add, Dreamweaver prompts a syntax error on line 37 in element.js, not sure if this is something that can be ignored?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Plugin: Jazzy Forms] Is this W3C validated?’ is closed to new replies.