He's only been there for a bit over 4 years, give him a break

Fair concern. My gut is yeah, people would probably end up building some weird, inaccessible stuff. I say that as someone who has committed their fair share of CSS crimes in the name of experimentation and seeing what's possible 😅

Clear would return the element to the unset state and set would set a specific (arbitrary) value. Combine that with recent css functions and custom properties and I bet you could implement some pretty complex interactions between just HTML and CSS

My original thought was add, remove, toggle commands to modify a single well known Boolean flag. That internal state could be exposed too CSS via a well known function, pseudo selector, or attribute

Then I thought about genericising that further with support for arbitrary (numeric?) values

The MDN page mentions request-close, but I don't see that in the spec

Is the aim to offer a set of built in commands that operate on the element specified in the commandFor attribute? I'm imaging a basic set of commands like set, clear, and toggle that devs could work with without JS

Oh, interesting!

On first read MDN's description of it as "a way to declaratively assign behaviors to buttons…" scared me 'cause I thought there would be no way to adjust bindings after initialization, but it's all standard element attributes and such. Nice :D
developer.mozilla.org/en-US/docs/W...

Non-trader, thank you

Why no games? Games are good

Hoping for the best 🫰

Oh, those are quality ears too!

It's the technique a given designer uses to prepare their coffee or tea before starting the work day

The rules are for you, not them

Very good temple

Morning!

I keep hitting annoying keyboard usability bugs every time I pick up my iPad

- floating keyboard moving around unusably when positioned too close to the bottom of the screen
- in iPhone compatibility mode, the keyboard gets stuck on press-and-hold keys
- unfinished graphics on the floating keyboard