westbrook@stefanfrede the #webComponentsCG is working through some early conversation around #declarativeCustomElements and a further reduction of JS in interactive web applications. Come join the convo! https://discord.gg/hFNrXAdz
Nathan KnowlerI see “actions” as a primitive for custom elements.
For example, the `<dialog>` element have `showModal`, `show`, `open`, `close`; popovers have `togglePopover`, `hidePopover`, `showPopover`; and so on.
For declarative custom elements, we need a way to describe actions. An action might set CSS custom state or internal ARIA or set a form value or have effects on other elements inside (or outside?) of a shadow tree.
Actions then become something we can map events to or become something that invokers can target.
Perhaps if actions are abstract enough, we can reuse them between custom elements and attributes too — or tap into actions that exist in built-in elements.
