Unfortunately following an incident with a broken Lisp machine, a liquid lunch, and an unlicensed particle accelerator, I became trapped in a parallel universe where the HTML ERB anointed CSS by mistake during a drunken night out in Oslo.
The fundamental concept of CSS (best revealed by H.W.Lie's thesis IMO¹) was to create a rich and versatile and non-Turing-complete set of structural selectors in lieu of DSSSL's recursive logic, and to allow styles to overlay one another; two design choices that only by the application of gallons of irony can explain why most web pages are composed of a bunch of nested DIV elements with hashed IDs, overburdened class attributes, and assets compiled into static files.
"We'll have one style for the browser and one for printing!" - but turns out that nobody really gives a crap about printing, and when they do they want stuff printed exactly like it looks on screen.
"Forget tables, we'll have stuff floating around the screen!" - but turns out that there are more requirements for positioning rules that can be contained in anyone's philosophy.
Etc etc...
Mostly though you're upset because respectable computer scientists didn't get invited to those sorts of parties.
“The Web That Never Was”: https://youtu.be/8JOD1AQGqEg
I've thought about something similar, but for hardware--what if some early hardware design choices had went in a different way?
For example consider cathode ray tube (CRT) displays. A different choice by the CRT pioneers and we might have ended up with CRTs that scan outward in a spiral from the center, instead of scanning in a series of stacked left to right rows.
That would make bit mapped displays a lot more complicated. God help the programmer who has to write BITBLT for a spiral scan display.