Administration: Fix submenu cursor inconsistency in collapsed admin m…

[SwapnilWordpress]

Administration: Fix submenu cursor inconsistency in collapsed admin menu.

Props mazharulrobeen.
Fixes #65250.

What?

Fixes inconsistent mouse cursor behavior for the first submenu item in collapsed WP-Admin sidebar menus.

Problem

When the admin sidebar is collapsed, the first submenu item (.wp-submenu-head) does not display the expected pointer cursor on hover, while the remaining submenu items behave correctly.

The submenu item remains clickable, but the inconsistent cursor behavior creates a UI/UX inconsistency.

Solution

Adds a pointer cursor rule for:

.js #adminmenu .wp-submenu .wp-submenu-head {
	cursor: pointer;
}

This ensures consistent hover interaction behavior across all submenu items.

Testing Instructions

1. Open WP-Admin
2. Collapse the admin sidebar using “Collapse Menu”
3. Hover over a menu item with submenus (example: Tools)
4. Hover over the first submenu item
5. Verify the pointer cursor now appears correctly

Before

be.mp4

After

af.mp4

Trac ticket: https://core.trac.wordpress.org/ticket/65250

Use of AI Tools

AI assistance: No

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props swapnil1010.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.