Skip to content

Classic Editor: Support pasted WebP image URLs in TinyMCE smart paste - #12718

Draft
id7368 wants to merge 1 commit into
WordPress:trunkfrom
id7368:agent/classic-editor-webp-smart-paste
Draft

Classic Editor: Support pasted WebP image URLs in TinyMCE smart paste#12718
id7368 wants to merge 1 commit into
WordPress:trunkfrom
id7368:agent/classic-editor-webp-smart-paste

Conversation

@id7368

@id7368 id7368 commented Jul 27, 2026

Copy link
Copy Markdown

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

Summary

This updates the bundled TinyMCE paste plugin so Classic Editor smart paste recognizes direct WebP image URLs and inserts them as images, matching the existing JPG/PNG/GIF URL behavior.

Why

WordPress supports WebP images, and current TinyMCE documents images_file_types as affecting which image URLs are recognized and placed in an img element by smart_paste. Its default list includes webp.

Testing

  • Verified the minimal regex behavior on LC1:
    • .jpg, .jpeg, .png, .gif, .webp, and .WEBP image URLs are recognized.
    • .svg, query-string URLs, and non-absolute URLs keep the previous behavior.
  • Ran JavaScript syntax checks for the modified TinyMCE paste plugin files on LC1.

Copilot AI review requested due to automatic review settings July 27, 2026 15:15

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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

2 participants