keithamusOpinion poll!
You have a <button>, it makes a <foo> open. What would be the best declarative attribute for the button to control the foo?
<button clickaction=open
<button invokeaction=open
<button command=open
Other (comment ideas)
Poll ended at .
Sara Joy 
@keithamus I'm slightly confused by this - would there then be another attribute that gives the id of the <foo> element?
@keithamus and can't we have the attribute be called `action` even if one already exists in <form>s?
So maybe like:
```
<button action="open" controls="my-dialog-id">Show options</button>
```
I guess for a dialog we might also have a "showModal" action available... 🤔
@sarajw it might be confusing with forms, but if I'm happy to try if there's a strong desire from the community.
@keithamus it just seems perfectly fitting to me. And I used "controls" because I was thinking of aria, but just target would be great.
Luke@sarajw @keithamus So one thing to add is there's a 2nd type of 'thingy' which acts on interest (hover/focus/etc) rather than invoke(click), and the idea is they could be used at the same time. Not to say 'action' is bad but it's worth considering that bit too.
@Lukew @keithamus interesting! Fair play, naming is hard and I'm an outsider just speaking my mind :)
I'm stoked for this though. Feels like how buttons *should* work. But if inline JavaScript was a security issue, how is this safer? Just a lot less flexible and more hardwired?