Description
1. Summary
It would be nice, if HTMLHint documentation will contain arguments, why HTMLHint users must use specific rules.
2. Argumentation
“Must” in The script tag can not be used in head., Id and class value must meet some rules: underline, dash, hump. is not argument. The documentation does not show the reasons. Users should know “Why must”?
3. Example of expected behavior
As for CSSLint wiki. Examples:
adjoining-classesrule use, because Internet Explorer 6 doesn't support adjoining classesfallback-colors, because Internet Explorer 8 doesn't supportrgba()hsl()orhsla()
HTMLHint wiki doesn't contain similar argumentation.
4. Specific rules
At first, I want to know argumentation for these rules.
4.1. head-script-disabled
Most popular Stack Overflow answer with 1608 stars at March 2019:
The current state-of-the-art is to put scripts in the
<head>tag and use theasyncordeferattributes. This allows your scripts to be downloaded asap without blocking your browser.
Script tag must be used in head.
4.2. id-class-value
BEM — the most popular CSS methodology use underlines and dashes both. Example from BEM quick-start:
<!-- `search-form` block -->
<form class="search-form">
<!-- `input` element in the `search-form` block -->
<input class="search-form__input">
<!-- `button` element in the `search-form` block -->
<button class="search-form__button">Search</button>
</form>Users don't need use underlines or dashes.
5. Do not offer
Yes, I know, that I can enable/disable/modify specific HTMLHint rules. My question not about it.
Thanks.