3 ms·
But... I am, surely, not advocating for people using <b> now: I'm merely lamenting that we allocated a one-character tag for <b> and then resorted to a five-cha
by saurik 2y ago
But... I am, surely, not advocating for people using <b> now: I'm merely lamenting that we allocated a one-character tag for <b> and then resorted to a five-character tag for <strong>, as it affects the readability (I couldn't care less about how many characters it is to type) of the un-rendered/hand-written document.
(Hell: it isn't even clear that I'm "advocating" for anything at all; at best it would be "don't bother with HTML/Markdown, as both ended up making poor choices for readability of your source document: instead, use a custom markup/markdown and then have code--on your server--to render it into the appropriate semantic HTML". Yet, while that is how my blog used to work, I actually failed to reallocate the tag names.)
I do, in fact, carefully use <strong> in my HTML documents (though I'm now starting to wonder if that's wrong, per the sister comment which linked us to the standard; it, surprisingly-to-me, does seem like I'm "supposed to be using" <i> in most, if not all, of the places I've been using <em>...), and I've been known to go to pretty extreme lengths to correctly support various accessibility technologies in my code, both on the web and native.
It simply makes me a bit angry, every time I see it, that someone decided to make such a common element <strong> instead of, say, <s>, which I believe is a reasonable position and has nothing to do with accessibility, as we could have named the new tag <powerful> and it would have worked the same and yet clearly that would have been even worse than <strong> ;P. We should get to separately judge--and even potentially lament one of--these two decisions.
(I'm thereby going to assert pretty directly that your decision to insult me by calling a narcissist is based on you not bothering to read what I wrote or pay attention to the actual thing I was complaining about--as I'd in fact have no reason to complain if I didn't care about the same thing you do: no one removed <b> from either the standard or the implementation--and just ran with a knee-jerk interpretation of some of the keywords I used.)
- TheRealPomax 2y agoNote that times have changed, and what <b> used to be for back in the <font> and <center> days is not what it's still for. It's just a letter now, not short for "bold", with the following official definition: > The b element represents a span of text to which attention is being drawn for utilitarian purposes without conveying any extra importance and with no implication of an alternate voice or mood, such as key words in a document abstract, product names in a review, actionable words in interactive text-driven software, or an article lede. Same for <i>: that's not short for "italic" anymore, it's just a letter now, and is defined as: > The i element represents a span of text in an alternate voice or mood, or otherwise offset from the normal prose in a manner indicating a different quality of text, such as a taxonomic designation, a technical term, an idiomatic phrase from another language, transliteration, a thought, or a ship name in Western texts. So go nuts: don't use <strong> or <em> if you semantically just needed <b> or <i>.