Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter zberno

    (@zberno)

    Hi Jules,
    thank you for the support.
    I think I found the problem in the theme datepicker (ab-datepicker not the CF7 jqueryUI original one).
    So I think the IE11 dataset object issue is related to a sort of DOM alteration by my datepicker.
    Current status:
    – CF7 conditional fields v1.9.14 (untouched original code);
    – CF7 v5.2.2;
    – Removed custom datepicker;
    – Added CF7 fallback datepicker: add_filter( 'wpcf7_support_html5_fallback', '__return_true' ); in functions.php;
    – Now IE11 does not show errors.

    With this setup:
    – Modern browsers show native datepicker (ok for mobile, not very good for desktops)
    – Browsers with unsupported type=”date” input show jqueryUI datepicker but when date is picked the input shows the date in ISO format (yyyy-mm-dd) (very confusing for users but this is the only configuration for a correct CF7 form validation)

    Thanks for all the support

    • This reply was modified 5 years, 7 months ago by zberno. Reason: wrong snippet code
    • This reply was modified 5 years, 7 months ago by zberno. Reason: clarification

    Hi Jules,
    Thanks for the plugin!
    I think there is something more with IE11.
    with the plugin updated to 1.9.13 the IE11 console says:
    SCRIPT5007: Unable to get property ‘contains’ of undefined or null reference
    scripts.js (1115,5)
    if you want see it in action please visit: http://www.tep.pr.it/azienda/contatti/area-clienti/suggerimenti-e-segnalazioni/
    Thanks a lot!

    • This reply was modified 5 years, 8 months ago by zberno.
    • This reply was modified 5 years, 8 months ago by zberno.
Viewing 2 replies - 1 through 2 (of 2 total)