1. Attributes of the form xmlns:prefix must not be used in HTML (but can be used in XHTML).
Example:
2. Instead of the "name" attribute, use the "id" attribute. More: This "a" tag uses one or more entirely obsolete (in HTML5) attributes which must not be used in HTML5 documents. The HTML5 obsolete attributes for "a" include: "charset", "coords", "datafld", "datasrc", "methods", "name", "rev", "shape", and "urn". This message is displayed up to 5 times.
Example:
Example:
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
4.[64] '&' did not start a valid character reference in the value for "href" ("&target" is an invalid character reference). "⌖" is a recognized entity but the trailing semicolon appears to be missing. If this is not a character reference then encode the ampersand as "&".
Example:
...></a><a class='goog-inline-block share-button sb-blog' href='http://www.blogger.com/share-post.g?blogID=7162135601108734039&postID=4571131736230013529&target=blog' onclick='window.open(this.href, "_blank", "height=270,width=475"); return false;' target='_blank' title='BlogThis!'><span class='share-button-l...
5. The "g:plusone" tag specifies an undeclared namespace prefix "g"
Some website offer services to fix these issues regarding issue between new html 5 standards and previous blogger version . You may avail them at a price. However if you wish not buy any of their html coding and validation services, you may start to tweak the codes one by one. Another issue that many bloggers face is that they cannot entirely edit the html code to alter any errors audited by validation tools such as CSE HTML and W3C HTML rendering your website or blog to be unstable. In fact, I am also encountering these kinds of issues and hopefully someone can help us solve this errors.
No comments:
Post a Comment