That I completely agree with -- I've had a hot-take a couple of times in the past and I still hold to it, that regardless of what HTML was intended to be or no

That I completely agree with -- I've had a hot-take a couple of times in the past and I still hold to it, that regardless of what HTML was intended to be or not be originally, today it's at its best when it's treated as a user-facing rendering target, and a lot of the criticisms about HTML's ability to handle things like giant virtual lists are missing the point that you shouldn't have giant lists in your UX in the first place, you shouldn't have a DOM tree that lists out 20,000 options in a `ul` if you're treating HTML like it's a user-facing interface rather than an authorship format for the developer alone. I'm still honestly a firm believer in the design technique of designing the HTML of a website before I start working on the CSS, and I know that a lot of people call that naive or say that it doesn't work... but I'm not saying that you can't revise the HTML later to fit a design, just that first I want to know what the content is and I want to treat the HTML as a primary rendering target, not an authoring language. I think there are a lot of benefits to that (one being that in addition to being more user-controllable and flexible, it also makes it much easier to do responsive design if you approach web design through that lens because page layouts become views of a unified block of content rather than completely separate isolated designs). But I don't think including the CSS is where that process falls apart or that it's disrespecting the user or denying agency. It's like how if someone hands me a image of a block of text, my problem is not that the contrast in the image is too light or that it's the wrong color; my problem is that they handed me an image of a text document. If someone hands me a website that is so intrinsically tied to CSS that it's impossible for me to easily adjust column widths, that coupling is the problem more than the column widths. Firefox does have some some great options around CSS control for partial or small adjustments but in typical Firefox fashion its best features are all hidden like Mozilla is embarrassed of them. I didn't bring up userContent.css to be dismissive; genuinely you should take a look at it if you've never used it before. I make heavy use of it for websites, everything from building grayscale modes when I want a website to be less distracting, to swapping layouts around. But it's a valid criticism that it's not user-facing and you need to go into advanced settings to even enable it. Browsers could do more.