W3C Error – Stray start div tag

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Nick Diego

    (@ndiego)

    Hi Angela,

    There is something funny going on here. On the page you linked to, there is the correct gch-header div within the site-content div. This is the one generated by the plugin. But then there is a second one right before the closing body tag (i.e. </body>). This is what it looks like, I pulled this from the inspector:

    <div class="gch-header" style="background: url(https://www.structuralbuildings.com/wp-content/uploads/2015/10/SB-HEADER_3.jpg ) !important;
background-size: cover !important;
background-repeat: no-repeat !important;
background-position: top left !important;
width: 100%;
min-height: 400px;"></div>

    Was this code added manually somehow? I don’t see how this could have been generated by the plugin for a couple reasons. First, the plugin cannot hook content into this location. And second, this div does not have the markup of the plugin. The general markup looks like this:

    <div class="gch-header">
    <div class="gch-header-inner ">
        <div class="gch-header-image">
            <div class="gch-header-image-inner"> ....more code....</div>
        </div>
    </div>
</div>
    Thread Starter angeladesign

    (@angeladesign)

    Hi. This info was added to page.php due to this resolved issue: https://www.ads-software.com/support/topic/non-responsive-header-images-1?replies=5

    Let me know your thoughts – thanks.

    Plugin Author Nick Diego

    (@ndiego)

    Hi Anegla,

    This was a bit tricky to discover, but you have added that <div> incorrectly. I am not sure how it was added, but it is being loaded after the closing </html> tag. What is weird is that if you look in the inspector, it seems to try and correct the markup and it places the <div> inside the closing </body> tag. However if you look at the raw page source the <div> is in fact outside the <html> tags. This is what is causing the issue on W3C. If you look closely at the validator results, it shows you the same thing. A </html> tag right before the the <div> in question.

    This issue is not related to the plugin, so I am going to mark this as resolved from a “plugin issue” perspective, but if change how the <div> is being loaded on the page, the W3C error should go away.

    Best,
    Nick

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘W3C Error – Stray start div tag’ is closed to new replies.