Luke Warlow

But an idref wouldn't work for an element that's not on the page (read this as in the DOM)? So that react use case wouldn't work? In that case you'd...

> For the custom case, maybe a wild idea, but invoketarget could call an API on the element which custom elements could then override (bikeshedding very much welcome) Could we...

For the custom case auto would need to be handled in JS, but then so would an explicit action. I don't think requiring an action be defined alleviates any issues...

This wont impact on the auto for built in elements but https://github.com/openui/open-ui/issues/900 might be worth thinking about alongside this issue too.

Does requiring an explicit action actually help fix the ambiguity? Aren't we always going to rely on the invokee element in some form? Such as for the toggle action? If...

I feel like there must be some CSS selector that will allow styling an invoker button based on the targets state. But I can't think of a foolproof way off...

Disclaimer I haven't given OpenUI's tab research a read through yet so apologies if this is crazy talk. I will give it a read tomorrow these are just some late...

Linking https://github.com/openui/open-ui/issues/622 to continue the styling discussion

> Right now this isn't accounted for in the proposal. I think that's okay? Perhaps this establishes a use case for a `` 😜? See https://github.com/openui/open-ui/issues/957

For me it would make sense for cancel buttons to cancel and submit buttons to close. Given we can't know the intent for toggles I think close is the better...