Also iframes that can automatically size to their content.

Would also love to be able to conditionally disable elements with CSS. Similar to "pointer-events: none" but also covering keyboard and other interactions.

Combined with my previous request for a ":navigating" pseudo-class, this could be used as to prevent double form submissions:

I would love a way in CSS to detect when a navigation has been triggered by a link, form, or button that submits a form.

This would allow us to provide better visual feedback that a navigation is underway. Especially useful if the network is slow.

Hypothetical examples:

A list of users that just happens to be sorted alphabetically can be a <ul> (unordered list), because the nature of those users isn't affected by what order they're presented in - there's no special meaning to the order itself.

I know this was a shitpost, but for the sake of anyone who genuninely isn't sure: <ol> should be used for lists where the order itself conveys meaning, and implies a relationship from one item to the next. e.g. links in a breadcrumb or steps in recipe.

Correction: I'm told that the SvelteKit benchmark does actually perform the same work as next.js. The "vanilla" benchmark, though, generates like 3x the HTML.

A note of caution, however. This particular syntax will select not only the parent, but all of its ancestors as well.

Use :has(>&) to select only the direct parent.

The old horrors, I'm resigned to. It's the new, fresh hells I resent.

As for your juniors, the correct response is that building appreciation for the platform below you and building for it more effectively are the path to senior and beyond, not shipping more features or writing more code. Seniority requires taste, and taste requires understanding.