Skip to content

feat: rename "Screen Options" to "Display Options"#9823

Open
coderGtm wants to merge 1 commit intoWordPress:trunkfrom
coderGtm:feat/update-screen-options-text
Open

feat: rename "Screen Options" to "Display Options"#9823
coderGtm wants to merge 1 commit intoWordPress:trunkfrom
coderGtm:feat/update-screen-options-text

Conversation

@coderGtm
Copy link
Copy Markdown

@coderGtm coderGtm commented Sep 10, 2025

This pull request updates the terminology across the WordPress admin codebase, replacing "Screen Options" with "Display Options" for consistency and clarity in both user-facing text and internal documentation. The changes affect JavaScript, PHP, and CSS files, as well as help text, comments, accessibility announcements, and privacy policy documentation.

User-facing text and accessibility updates:

  • All references to "Screen Options" in UI strings, help text, and accessibility announcements have been changed to "Display Options" throughout the admin dashboard, post/page editors, and related screens. [1] [2] [3] [4] [5] [6] [7] [8] [9]

Documentation and code comments:

  • Inline comments, function descriptions, and documentation blocks referencing "Screen Options" have been updated to "Display Options" in both JavaScript and PHP files, including class properties and method descriptions. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

CSS class and section comments:

  • CSS comments and section headers have been updated to reflect the new terminology, ensuring style definitions and documentation are consistent with the new wording. [1] [2] [3] [4] [5] [6]

Privacy policy and cookies:

  • The privacy policy text now refers to "display options cookies" instead of "screen options cookies" to match the new terminology.

These changes ensure a unified experience and reduce confusion for users and developers by standardizing the term "Display Options" throughout the WordPress admin interface and codebase.

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

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
Copy link
Copy Markdown

github-actions bot commented Sep 10, 2025

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

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

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 10, 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

@coderGtm