61–70 of 138 posts
Earlier quoted context omitted.
most specifically the problem is that markdown tables don't allow breaking the table row in multiple lines but then you can always use HTML tables in markdown and Pandoc transforms it just fine
has worked fine whenever I’ve needed line breaking in markdown tables
It shouldn’t be so controversial to say that if 99% of usage routes around your API, it’s probably the API’s fault.
The GOV.UK Design System summary list component is a description list https://design-system.service.gov.uk/components/summary-list... And... it also uses the wrapper div for styling
The wrapper div is making me a bit sad. These days, using grid layout, you don’t actually need it in most cases
I put dl lists in a grid with no divs needed. As MDN says, div is the last resort, invariably there is something better, and nowadays that is grid styling.
New to me is multiple dd's.
For legacy layouts littered with divs and classes, display: contents helps get rid of the div wrappers, promoting whatever is wrapped.
Even with disclosure elements there are ways to avoid div wrappers using the pseudo element for everything enclosed by the details element apart from the summary element.
This is going to be unpopular here, but life became easier when I quit trying to write semantic HTML. It’s just poorly designed, I’m sorry. Every time I’ve reached for a I’ve eventually regretted it because I wanted multiple levels of wrappers, or a divider between sections, or an icon, or a heading spanning multiple key-value pairs, etc. They make this stuff with some flexibility but nowhere near enough to actually…
:wrap(dt, dt+dd) {border: solid 1px}I was a bit surprised to see nested s given as some sort of precursor pattern, when was part of HTML before 2.0 back in the days of table layout.
Earlier quoted context omitted.
most specifically the problem is that markdown tables don't allow breaking the table row in multiple lines but then you can always use HTML tables in markdown and Pandoc transforms it just fine
has worked fine whenever I’ve needed line breaking in markdown tables
The GOV.UK Design System summary list component is a description list https://design-system.service.gov.uk/components/summary-list... And... it also uses the wrapper div for styling
The wrapper div is making me a bit sad. These days, using grid layout, you don’t actually need it in most cases
I don't really like the div either (I use the design system all day, and maintain a set of components), but it makes documentation much easier.
The tag seems to cover a subset of a broad semantic space, but doesn’t easily extend beyond adding another . I dunno, I guess I’m a caveman. If it looks right and works (including accessibility) then I figure I’m pursuing something that doesn’t matter a lot.
Shameless plug: you might be interested in https://calvinlc.com/p/2026/02/11/everything-is-a-div.html I need to learn more about web accessibility, but if you completely ignore it (and other sane practices) HTML looks really simple. I think the design of HTML is just too much. There’s so many tags that don’t do much. It’s like w3c decided that any common thing people use in websites needs a tag. The end result is mor…
I’ve noticed that discussions of semantic meaning of tags often contain the word “feel.” Nothing wrong with that, taste matters, but it does point to the non-functional goals that are being pursued when people disagree.
vs - they are both ordered, because markup is ordered. One gets decorated differently than the other by default. Is the difference semantic or typographical?
Am I the only one?