-
Notifications
You must be signed in to change notification settings - Fork 22.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add documentation for the "command" and "commandfor" attributes, and "command" event. #30829
Conversation
(Converted to draft so that nobody review this, yet) |
Preview URLs (9 pages)
Flaws (2)Note! 7 documents with no flaws that don't need to be listed. 🎉 URL:
URL:
(comment last updated: 2024-10-17 19:46:10) |
This pull request has merge conflicts that must be resolved before it can be merged. |
daeba33
to
dd68146
Compare
dd68146
to
48a6f67
Compare
48a6f67
to
bbc194f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks; I have a lot of nits proposed, but I think this looks good already.
Co-authored-by: Joshua Chen <sidachen2003@gmail.com>
Should I wait for the other reviewers to make a final pass? |
Given it's been three days since your comment perhaps the "waiting for other reviewers" has passed anyway? (Not a judgement btw). |
I'll merge this some time next week. |
|
||
{{DefaultAPISidebar("Invoker Commands API")}} | ||
|
||
The **Invoker Commands API** provides a way to declaratively assign behaviors to buttons, allowing control of interactive elements when the button is enacted (clicked or invoked via a keypress, such as the spacebar or return key). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps "enacted" could be replaced with another word. It doesn't quite read naturally to me. Maybe "activated", idk what the normal word mdn uses is.
The preview suggests there's issues with the browser compat data is that expected? |
Is it worth mentioning the requirements around explicit type attribute when inside a form? |
I think the only issue is that there's no spec URL, which is kind of expected given that whatwg/html#9841 is still open. @keithamus if you want to make an issue to BCD to keep it in the backlog it would be great. |
@keithamus Just waiting on the last bits of reviews to be addressed |
Co-authored-by: Luke Warlow <luke@warlow.dev>
|
Co-authored-by: Scott O'Hara <scottaohara@users.noreply.github.com>
@lukewarlow Let me know when this is good to merge |
Lgtm! @keithamus do we want to wait for the html pr? |
It doesn't seem necessary to me to wait but if people would like to I don't mind. |
Thanks for all the work everyone; since we have BCD already, I think this meets the documentation criteria and we can merge it. |
Description
This PR drafts up the documentation for "Invokers" (OpenUI explainer). This is a new experimental API for enabling buttons to control interactive elements.
Motivation
As this feature is starting to land (flagged) in 3 major browsers, it seems right to start documenting the featureset.
Additional details
dom.element.invokers.enabled
flag.Related issues and pull requests