Opened 5 months ago
Last modified 2 months ago
#64576 assigned enhancement
Add support for invoker command attributes
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 7.1 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | General | Keywords: | has-patch has-unit-tests |
| Focuses: | ui, accessibility, javascript, css | Cc: |
Description
Similar to the support added to popovers, invoker commands are now baseline, and should be allowed in post content.
See #61959.
Change History (5)
#2
@
5 months ago
Related:
- gutenberg#69363: Make the navigation block content available when JavaScript is disabled
- gutenberg#69720: Navigation block: use
<dialog>
This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.
3 months ago
This ticket was mentioned in PR #11483 on WordPress/wordpress-develop by @pratiknawkar94.
2 months ago
#5
- Keywords has-patch has-unit-tests added; needs-patch removed
Allow the Invoker Commands API attributes command and commandfor on <button> in $allowedposttags so post content sanitization (wp_kses_post()) no longer strips them. This matches existing support for popovertarget / popovertargetaction from the Popover API work (#61959).
Adds a PHPUnit test that verifies a button with command / commandfor and a popover target survives wp_kses_post().
E.g., see documentation in https://developer.mozilla.org/en-US/docs/Web/API/Invoker_Commands_API, article at https://schalkneethling.com/posts/opening-and-closing-dialogs-without-javascript-using-html-invoker-commands/