Remix.run Logo
extra88 an hour ago

Eh, it's fine, elements should be defined for what they mean, not what they look like. The explanation and distinctions made between <b> and other elements (<i>, <em>, <strong>) make sense.

The suggested (not obligatory) user agent styling for <b> is `font-weight: bolder` an agent or authors could use lots of different things to bring attention to what the element contains and treat it differently from <strong>.

https://html.spec.whatwg.org/multipage/text-level-semantics....

https://html.spec.whatwg.org/multipage/rendering.html#phrasi...

sunshowers an hour ago | parent [-]

I write most of my content in markdown or asciidoc and I don't pay attention to whether it's b or strong :)

extra88 38 minutes ago | parent [-]

In practice today, that's fine. Typically authors have a hard time differentiating what "emphasis," "importance," and "bring attention to" mean to them. Therefore, nothing conveys a distinction by default.

sunshowers 29 minutes ago | parent [-]

So then what's the point of making this distinction? I would like to see surveys of how many people actually author content in forms that differentiate between b and strong.