wordpress-develop icon indicating copy to clipboard operation
wordpress-develop copied to clipboard

Customizer: Add tooltips to responsive preview icons for improved usability

Open himanshupathak95 opened this issue 10 months ago • 3 comments

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

This PR adds tooltip functionality to the responsive preview icons in the WordPress Customizer. By displaying tooltips on hover, users can now clearly identify the purpose of each device preview button before clicking them, enhancing usability and accessibility.

The implementation:

  • Uses aria-label attributes for tooltip content, which maintains accessibility
  • Follows UI patterns similar to tooltip implementations elsewhere in the admin

Before

https://github.com/user-attachments/assets/432bf2ec-3779-4e9e-ba77-cdbd2e77f04a

After

https://github.com/user-attachments/assets/45085d9d-05a8-4eb9-90f8-0525a135d1e4

himanshupathak95 avatar Mar 26 '25 07:03 himanshupathak95

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 abcd95.

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

github-actions[bot] avatar Mar 26 '25 07:03 github-actions[bot]

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

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • 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.

github-actions[bot] avatar Mar 26 '25 07:03 github-actions[bot]

The failing tests seem unrelated to the changes made in the PR.

himanshupathak95 avatar Mar 26 '25 07:03 himanshupathak95