The thing is there is no hivemind best practice. It depends on a lot of factors such as team size, project duration, technology stacks, etc... As you may already know being able to spot pros and cons ahead of time and avoiding pitfalls for a specific scenario just comes from experience. So if anyone is uncertain about how to proceed, the only way you can become more comfortable in decisions is to try all the things and learn the nuances of different approaches. Eventually it becomes much more natural and requires less effort.

Does this mean never put style strings in html? Whether by style-attr, JS or CSS, that html tree has to get style attributes somehow.

I sort of accepted a similar view, that functionality and presentation should be separate (although base html isn't necessarily representative of either).

Now have a more nuanced view: functionality and presentation don't map strictly to logic (js) and style (CSS) - I think there is such a thing as presentation logic, versus data logic.

It was only considered super bad by a subset of people. Usually not the people creating and maintaining web apps.

The "subset of people" known as "good developers." Lately they haven't been creating and maintaining web apps because of things like Tailwind.

Pretty sure ‘good developer’ wasn’t the discriminating factor.

This will almost surely happen.

CSS will be extended until it solves the pain points, at which point things will swing in the other direction.

It's just a question of where your abstraction point is. Currently it's in a component. Tomorrow it might move.