3 ms·
The point is that the marketing is false. This CSS framework forces to you to abuse HTML semantics if you want to use it, which is exactly what it claims it doe
by larsga 6y ago
The point is that the marketing is false. This CSS framework forces to you to abuse HTML semantics if you want to use it, which is exactly what it claims it doesn't do.
What's extra frustrating is that it would be so easy to fix, by just adding a few classes. But they wanted to be "semantic", so they forced their users to be unsemantic.
- IggleSniggle 6y agoOr they could have just used arbitrary elements, like <myelement>. Folks forget that this is valid HTML, and it’s just treated as a div.
- recursive 6y agoI don't think they forgot, because it was never true. It needs a dash `-` in it. https://html.spec.whatwg.org/#valid-custom-element-name https://html.spec.whatwg.org/#valid-custom-element-name
- folmar 6y agoIt needs them now, but it wasn't always the case. In html5-20121025 User agents must treat elements and attributes that they do not understand as semantically neutral. It was also in the grey area in HTML4.01 spec, note B.1 provides for user agents rendering any unknown elements.