Would non-IE browsers throw mixed content warning?

  • TWD

    (@twd)


    1 year, 2 months ago

    Supposing I have IE conditional comment tags like this as part of the theme:

    <!--[if IE]>
<script src='https://mysite.com/wp-content/themes/astra/assets/js/minified/flexibility.min.js?ver=3.9.4' id='astra-flexibility-js'></script>
<script id='astra-flexibility-js-after'>
flexibility(document.documentElement);
</script>
<![endif]-->

    Would non-IE browsers throw a “mixed content” warning in the browser bar if the “src” attribute of the first script referred to a site without a valid SSL certificate?

    OR would this simply not be parsed at all because it’s technically a HTML comment?

Viewing 3 replies - 1 through 3 (of 3 total)
  • George Appiah

    (@gappiah)

    1 year, 2 months ago

    Do you have a “non-IE browser”?

    Test, test, test!!!

    Thread Starter TWD

    (@twd)

    1 year, 2 months ago

    Yes, it’s something that would normally be easy to test.
    However, my circumstances are a bit unusual.
    The work is being done on a non-SSL certificate IP address so there is no way to really test until we migrate to the live domain.

    George Appiah

    (@gappiah)

    1 year, 2 months ago

    I’m sure you have a domain or subdomain you can use to create a simple HTML page online to test this. You don’t need WordPress.

    And if you absolutely must test this under WordPress, create a test site here in 10 seconds — no registration needed, and you have full access to the file system: https://instawp.com/

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Would non-IE browsers throw mixed content warning?’ is closed to new replies.