What CSS needs (opinion, caveat, really far away in advanced features) is:

- A way to get values from sliders (type="range") (and style and modify them easily). Really, a way to get "value" from any <input> element.

- A way to have radio / checkboxes or labels inside labels work for multiple choices (or something other than making enormous arrays of radio selections and CSS choices)

- A way to have indexed arrays of numbers / choices (other than using a crazy complicated animation timing trick)

- String concatenation thats not so incredibly finicky and difficult to implement correctly

- Some way to retain the final "state" of a condition without resorting to playing an animation on "forwards" mode. Also, related, some way to not require the hidden checkbox hack everywhere.

- (Advanced, lower priority) A way to force var() calculation and optimizations other than making a zillion @property statements. "This expensive trig calculation is used a hundred times later on, better make it a separate ... nvm, it gets regex placed into every other calculation on the entire page ... " ¯\_(-_')_/¯

- If() and Function() ... wait, /inappropriate_swear, we're actually getting these after a quarter century.

▲ nicoburns 5 days ago | parent [-]

It looks like HTML may be getting the ability to manipulate the class/attributes of elements in response to clicks (declaratively, without JS). Which would solve a lot of the interactivity issues (checkbox hack, etc).

See: https://developer.mozilla.org/en-US/docs/Web/API/Invoker_Com...

	▲	araes 5 days ago \| parent [-]
		Thanks. Saw this, thought it looked cool. Just could not find what it can do other than "popover" "popovertarget" without using JS. The examples provided for custom events all seem to use JS anyways. Ex: `<button commandfor="the-image" command="--rotate-landscape"> ... if ( event.command == "--rotate-landscape" ) { image.style.rotate = "-90deg" }` Agree it would be cool, it just doesn't seem to do a lot. Generalized "popovertarget" except that basically means +modal <dialog> in most of the examples. And all the modal dialogs are almost always "popover". And you can already make "popover" appear over "popover" with multiple onscreen. Maybe there's something with looking. [1] [1] https://developer.chrome.com/blog/command-and-commandfor Edit: Here's an example of the overlapping popover functionality. https://araesmojo-eng.github.io/ Main Page -> General Tests Menu -> Open Popover 1 \| Open Popover 2 Should both open popovers simultaneously on top of each other while dismissing neither, and also change the state of elements on the page at the same time.