This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

Replies

5
  1. Daniel Staff 11 years, 3 days ago

    Hi there,

    I have looked at your site but could see where the CSS error you mentioning is occurring. Would mind sending a direct link to the page in question?

    Looking forward to hear from you

  2. stacieb 11 years, 3 days ago

    Here is a link:
    newman.blueballoondesigns.com

    I am having issues when I run it thru the HTML validation, but I now have it worked down to just a few errors, and from what I can tell in your forum, the three remaining (that have to do with the vantage theme) are common and you are all aware of. Just wondering if this first error can be corrected?

    Line 5, Column 54: A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge.

    The last two I see you have stated in the past will remain.

    thanks for your help!

  3. stacieb 11 years, 3 days ago

    Correct. I am getting 6 errors when I use the validator. Not CSS errors. I see 6 HTML errors.

  4. Andrew Misplon Staff 11 years, 1 day ago

    Hi stacieb

    @mikeSo, thanks for your contribution here. Always appreciated.

    Thanks for reaching out.

    The Validator is worth checking out but it’s output isn’t cut and dry, for example we still need to use browser specific CSS “hacks” to help out some of the older browsers still in use. Those don’t pass the validator. That’s one example. Let me try run through the errors that you’re seeing:

    1.

    <meta http-equiv="X-UA-Compatible" content="IE=10" />
    

    This has come up before, I’ll leave it to stackoverflow to explain:
    http://stackoverflow.com/questions/14198594/bad-value-x-ua-compatible-for-attribute-http-equiv-on-element-meta

    Answer two does outline a possible fix. That would require a child theme and some work though. What’s important is that there isn’t a real error here.

    2, 3, 4, 5.

    These all come from the Angies List badge that’s been inserted in a Text widget. You might have tried to insert that twice. As a result the ID being used by the badge is on the page twice. Not a big issue but it’s causing an error.

    The other two errors come from the markup of the badge, the way the iframe is constructed.

    6 & 7.

    These are both coming from Meta Slider plugin. It’s another borderline case at first glance. stackoverflow has this too: http://stackoverflow.com/questions/18549726/element-link-is-missing-required-attribute-property
    Nothing to worry about there.

    Hope this helps explain things a little. Nothing serious in there.

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread