| ▲ | kevincox 5 hours ago | |
> It's certainly better than calling everything a div. It's not. For semantic purposes <my-element> is the same as <div class=my-element>. So on the surface they are equivalent. But if you are in the habit of using custom elements then you will likely continue to use them even when a more useful element is available so <my-aside> rather than <aside class=my-aside> so in practice it is probably worse even if theoretically identical. Basically divs with classes provide no semantic information but create a good pattern for using semantic elements when they fit. Using custom elements provides no semantic information and makes using semantic elements look different and unusual. | ||
| ▲ | jeremyjh 5 hours ago | parent | next [-] | |
> But if you are in the habit of using custom elements then you will likely continue to use them even when a more useful element is available This article is written for web developers. I’m not sure who you think you are addressing with this comment. In any case - the argument is a weak one. To the extent people make the mistake you allege they can make it with classed div and span tags as well and I’ve seen this in practice. | ||
| ▲ | ragall 5 hours ago | parent | prev [-] | |
> For semantic purposes But semantic purposes are not all possible purposes. | ||