You do remember the hell that was the font tag, don’t you? I think a lot of confusion from HTML being used for UIs vs hypertext documents. It’s a natural evol

You do remember the hell that was the font tag, don’t you? I think a lot of confusion from HTML being used for UIs vs hypertext documents. It’s a natural evolved mess still balancing the two. But style should apply to the applied representation, while HTML should represent the intent of the content. The line is fuzzy, and HTML/CSS has a bad history of what falls where. The cool thing with browsers is that we can bake in style to support multiple representations at once: monitor, mobile, printer, etc. Using the style attribute directly is mostly a side effect of only targeting the browser. Although your example of relative units is more ambiguous. Using a proper tag to represent the intent or falling back to a class where HTML lacks one would be preferable. I think the separation makes more sense if you’ve used other document systems. SGML or XML DocBook, LaTeX, ROFF, etc. For the last, if I use the man or mandoc module, all the man page norms are there for me and I’m just plugging in the content with the right macros. W/o, I’m manually flipping registers all over the place. But I’ve never hear of a roff or LaTeX UI, so…