You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I don't know that we ever discussed that or if we feel like the current custom commands is covering this, but I'd like to discuss whether this is useful
I also added #1068 separately for the sentences that immediately followed this- it feels related but also separate.
The text was updated successfully, but these errors were encountered:
In the w3c TAG review, there was a closing comment that
I don't know that we ever discussed that or if we feel like the current custom commands is covering this, but I'd like to discuss whether this is useful
I also added #1068 separately for the sentences that immediately followed this- it feels related but also separate.
The text was updated successfully, but these errors were encountered: