CommandUI 1.11.0 fixes two small but long-outstanding edge-case bugs and provides a better experience with WordPress default command palette.
Improved reliability during third-party plugin updates
CommandUI integrates with many plugins and uses their official ways to retrieve data, or use their functionality.
In some cases, this could lead to issues during WordPress updates of plugins, where third-party plugins might only be partially loaded internally but still appear to be fully active to CommandUI.
CommandUI now ignores all integrations when WordPress is updating, as there is no use for CommandUI during updates anyway.
Fixed shortcuts firing inside IFrame editors
CommandUI tries to be available everywhere inside the WordPress site and has global shortcuts to perform actions, such as “e” to edit a post or “v” to view a post in the frontend. These actions should only be available when the active mouse focus is NOT inside text areas or other interactive areas.
This detection works reliably but has historically struggled when page builders are loaded inside an iframe and/or use non-standard HTML elements as input.
CommandUI now defaults to NOT firing its shortcuts, unless it’s certain that it’s NOT from an interactive element. Previously, it was the opposite, and uncertainty fired shortcuts.
CommandUI unloads the default global command palette in WordPress 6.9 and newer.
This prevents two command bars and competing keyboard shortcuts from appearing in the WordPress admin. The native palette is removed only when CommandUI is available to the current user; otherwise, WordPress’s palette remains available.