Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter eclev91

    (@eclev91)

    FWIW, the workarounds in the linked article are more complicated than they need to be. It has nothing to do with space or semi-colons. Just getting the browser to repaint the field will fix it. I went ahead and hooked into admin_print_scripts to get this working for us in the meantime:

    add_action('admin_print_scripts', function() {
    ?>
    <script>
    document.addEventListener('DOMContentLoaded', function() {
    var emailInput = document.getElementById('customer_email');
    if (emailInput && navigator.userAgent.indexOf('Safari') != -1 && navigator.userAgent.indexOf('Chrome') == -1) {
    var emails = emailInput.value;
    emailInput.value = emails;
    }
    });
    </script>
    <?php
    });
    • This reply was modified 5 months ago by eclev91.
    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @eclev91

    We appreciate your detailed explanation and the workaround you’ve provided for the issue related to Safari’s rendering of multiple email inputs. It’s very insightful, and I’m sure this will greatly help others experiencing the same issue.

    However, it would be great if you added this as an enhancement or bug report to our GitHub repo here. This way, our developer can check and provide further insights.

    Meanwhile, I will mark this thread as resolved. Should you have further inquiries, kindly create a new topic here.

    Thanks!

    Thread Starter eclev91

    (@eclev91)

    @shameemreza Do you ask non-technical users to submit tickets on GitHub?

    Seems like the minimal thing that the WP.org plugin support team for Woo could do is translate technical bugs over to the GitHub repo.

    But now that I’ve debugged the issue that your support did not debug on a previous thread, I will also report it on the GitHub repo. I look forward to being asked to implement the fix as well.

    • This reply was modified 4 months, 1 week ago by eclev91.
    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @eclev91,

    We truly appreciate your diligence in identifying the issue and apologize for any inconvenience caused.

    In most cases such as yours, we encourage users, regardless of their technical proficiency, to report the issues they encounter. This is because my colleague was probably unable to replicate the issue, as this seems to only affect users running Apple devices.

    We appreciate your contribution to our community. Rest assured, our development team is responsible for implementing fixes, and your assistance in this matter is greatly appreciated.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.