News for hackers. Stuff that matters.
Re:Mvp.css – build your landing page with only semantic HTML by larsga on Saturday November 21, 2020 @04:53AM (#25168747)
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.

Re:Mvp.css – build your landing page with only semantic HTML by IggleSniggle on Saturday November 21, 2020 @10:18AM (#25170153)
Or they could have just used arbitrary elements, like <myelement>. Folks forget that this is valid HTML, and it’s just treated as a div.
Re:Mvp.css – build your landing page with only semantic HTML by recursive on Saturday November 21, 2020 @11:02AM (#25170371)
I 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

Re:Mvp.css – build your landing page with only semantic HTML by folmar on Saturday November 21, 2020 @01:04PM (#25171383)
It 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.

Re:Mvp.css – build your landing page with only semantic HTML by Conlectus on Saturday November 21, 2020 @01:23PM (#25171577)
Semantically neutral yes, but they are not divs -- they're "unknown elements", which have more annoying behavior (similar to pseudoelements from memory)
Re:Mvp.css – build your landing page with only semantic HTML by ehnto on Saturday November 21, 2020 @11:44PM (#25175001)
I think that's right. They start out life as inline-block elements.