Skip to content

Administration: Replace incorrect cite elements with span for author names #9935

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.

Sign up for GitHub

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

Jump to bottom
Draft
himanshupathak95 wants to merge 5 commits into
base: trunk
Choose a base branch
from
Draft

Administration: Replace incorrect cite elements with span for author names #9935

himanshupathak95 wants to merge 5 commits into from
+10 −5

Conversation

@himanshupathak95
Copy link

@himanshupathak95 himanshupathak95 commented Sep 17, 2025 •
edited
Loading

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

This PR fixes incorrect usage of <cite> elements for author names throughout the WP admin to comply with HTML5 semantic standards.

The HTML5 specification states that <cite> should only be used for titles of works (books, movies, songs, etc.), not for author names. This change replaces all instances where <cite> incorrectly wraps author names with semantically appropriate <span> elements.

  • Plugin Install List Table: Replace <cite> with <span class="plugin-author"> for plugin authors
  • Plugin Data Markup: Replace <cite> with <span class="plugin-author"> in plugin descriptions
  • Dashboard Comments: Replace <cite class="comment-author"> with <span class="comment-author">
  • CSS Updates: Add styling rules for new classes to maintain visual consistency

@github-actions
Copy link

github-actions bot commented Sep 17, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@himanshupathak95