Re: [w3ctag/design-reviews] Invokers API (Issue #920)

@hober, @plinss, and I discussed this today.

We're broadly in favor of invokers because it unifies some existing interaction patterns.

We feel it makes sense to have an `invoke(action, invoker)` method because it lays a path for future interactions with elements.  We think that this might be more useful for custom elements or future features that are added to the platform.

We observe that a lack of additional arguments to invocations (or `invoke()`) are a concession toward the declarative nature of the core feature.  Rather than a flaw, we see this as an important characteristic of the design.  It simplifies this design and this characteristic seems like it is worth protecting.  Richer interactions can remain the domain of script.

Having `invoke()` also helps discoverability.  We think that this would be more useful if it were possible to get the list of available actions from elements.

(A footnote from me: when we ask questions, like the one above about focus, we appreciate your helpful answers.  We appreciate those answers being added to documentation even more.)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/920#issuecomment-1989499571
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/920/1989499571@github.com>