Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Rick Curran

    (@rickcurran)

    Hi, after posting these I realise one potential reason for a span parent is to align it without affecting the child div elements and cascading the vertical-align styling down to them. If this is the case then perhaps switching the span to a div with a specific class so that the css can be applied only to it, e.g. div.cli-bar-parent.

    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @rickcurran,

    Greeting from CookieYes!

    We agree with what you’ve mentioned. Many of our customers found our solution to be effective. Since any modification to the HTML template could also affect current users, the workaround cannot be quickly implemented in our plugin.

    If it is possible, you can switch to our revamped interface by going to the Advanced tab and clicking on the “delete settings and reset’ button. The issue will not be there in the revamped interface. However, switching to this interface will wipe out all of your current configurations on the plugin, and you have to start from the beginning.

    We sincerely hope you can understand us.

    Thread Starter Rick Curran

    (@rickcurran)

    Hi @cookieyesteam, thanks for getting back to me. I followed those steps to switch to the revamped interface, however whilst this has resolved the issue with the span tag when validating the page it is now raising another error in the validator:

    Element style not allowed as child of element body in this context

    It’s highlighting the use of the following style block within the contents of the body tag:

    <style id="cky-style-inline">
    [data-cky-tag] {
        visibility: hidden;
    }
    </style>

    Is intentional that this style block is implemented this way and not within the head element as style blocks should be? If not can this be fixed?

    Thanks again for taking the time to reply!

    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @rickcurran,

    We agree with what you discovered. This has been added to our backlog. We’ll solve that in the plugin’s upcoming update. Will you be able to wait till then?

    Thread Starter Rick Curran

    (@rickcurran)

    Hi @cookieyesteam, thanks, great to hear it will get fixed in the next update. Thanks again for looking into these issues!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Invalid HTML in cookie notice markup’ is closed to new replies.