Skip to content

Editor: Print buttons stylesheet in wp_editor() when QuickTags is enabled - #14239

Open
wprashed wants to merge 1 commit into
WordPress:trunkfrom
wprashed:fix/64841-wp-editor-quicktags-buttons-css
Open

wprashed wants to merge 1 commit into
WordPress:trunkfrom
wprashed:fix/64841-wp-editor-quicktags-buttons-css

Conversation

@wprashed

Copy link
Copy Markdown

Description

When wp_editor() is rendered on the frontend with QuickTags enabled, the QuickTags toolbar renders buttons with the .button and .button-small classes. In WordPress 6.7, QuickTags buttons were migrated to use standard WordPress button classes whose base styles reside in buttons.css (handle buttons).

While editor.css (handle editor-buttons) is force-printed inline inside _WP_Editors::editor(), buttons.css is only enqueued in enqueue_scripts() at wp_print_footer_scripts. If wp_editor() is called after wp_head() has fired (as is standard in frontend templates or shortcodes), buttons.css was not output before the editor, leaving QuickTags buttons unstyled.

This PR adds a call to wp_print_styles( 'buttons' ) inside _WP_Editors::editor() when QuickTags is enabled (! empty( $set['quicktags'] )), ensuring the stylesheet is printed alongside editor-buttons and styling the QuickTags buttons correctly.

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


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.

…bled.

QuickTags toolbar buttons use the standard .button and .button-small classes whose base styling is provided by buttons.css. On the frontend, wp_editor() force-prints editor.css, but buttons.css was only enqueued, meaning it was not printed if wp_editor() was called after wp_head() ran. This left QuickTags buttons unstyled. This change ensures buttons.css is force-printed alongside editor-buttons when QuickTags is enabled.

Props vnoben, wprashed.
Fixes #64841.
@github-actions

Copy link
Copy Markdown

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

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

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.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant