4 ms·
> Because if your thing goes complaining when I write <li>item<li>item, I’ll be upset. And I'll be upset in the code review if you write HTML like that.
by knallfrosch 2y ago
> Because if your thing goes complaining when I write <li>item<li>item, I’ll be upset.
And I'll be upset in the code review if you write HTML like that.
- chrismorgan 2y agoWhen writing code with others, in existing code bases, I will follow house style. (More faithfully than almost anyone else, because I pay attention to these things, both to see what the style is, and to match it.) When writing code personally, I’ll omit things like </p>, </li>, </head>, </body>, </html>, <head> (which should never have attributes), and attributeless <html> and <body>. When writing code with others, if I’m in charge, I’ll frequently retain </p> for others’ sensibilities, but I will still often choose to omit </li> (depending on the type of code, definitely). I specifically dislike </li> because I’ve seen far more problems caused by its presence than by its absence—incorrect nesting and the likes. Also I reckon it’s good that you end up with no whitespace node between your list items (since any whitespace goes into the previous list item), mostly because of old-style `display: inline-block` and such.