Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>TL;DR</strong></p> <ul> <li>Custom tags are invalid in HTML. This may lead to rendering issues.</li> <li>Makes future development more difficult since code is not portable.</li> <li>Valid HTML offers a lot of benefits such as SEO, speed, and professionalism.</li> </ul> <p><strong>Long Answer</strong></p> <p>There are <a href="http://www.html5rocks.com/en/tutorials/webcomponents/customelements/" rel="nofollow noreferrer">some arguments</a> that code with custom tags is more usable.</p> <p>However, it leads to invalid HTML. Which is not good for your site.</p> <p><a href="https://stackoverflow.com/questions/1337928/whats-the-point-of-valid-css-html"><strong>The Point of Valid CSS/HTML | StackOverflow</strong></a></p> <blockquote> <ul> <li><a href="http://www.hobo-web.co.uk/seo-blog/index.php/official-google-prefers-valid-html-css/" rel="nofollow noreferrer">Google prefers it so it is good for SEO.</a></li> <li>It makes your web page more likely to work in browsers you haven't tested.</li> <li>It makes you look more professional (to some developers at least)</li> <li>Compliant browsers can render [valid HTML faster]</li> <li>It points out a bunch of obscure bugs you've probably missed that affect things you probably haven't tested e.g. the codepage or language set of the page.</li> </ul> </blockquote> <p><a href="http://validator.w3.org/docs/why.html#why_pros" rel="nofollow noreferrer"><strong>Why Validate | W3C</strong></a></p> <blockquote> <ul> <li>Validation as a debugging tool</li> <li>Validation as a future-proof quality check</li> <li>Validation eases maintenance</li> <li>Validation helps teach good practices</li> <li>Validation is a sign of professionalism</li> </ul> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload