Title: Media Editor Modal: call for testing
Author: ramonopoly
Published: May 21, 2026
Last modified: June 3, 2026

---

 [  ](https://profiles.wordpress.org/ramonopoly/) [ramonopoly](https://profiles.wordpress.org/ramonopoly/)
11:57 pm _on_ May 21, 2026     
Tags: [core-editor ( 764 )](https://make.wordpress.org/core/tag/core-editor/),
[gutenberg ( 555 )](https://make.wordpress.org/core/tag/gutenberg/), [media ( 93 )](https://make.wordpress.org/core/tag/media/),
[media modal ( 4 )](https://make.wordpress.org/core/tag/media-modal/)   

# Media Editor Modal: call for testing

The addition of a free-form image cropper in the BlockBlock Block is the abstract
term used to describe units of markup that, composed together, form the content 
or layout of a webpage using the WordPress editor. The idea combines concepts of
what in the past may have achieved with shortcodes, custom HTML, and embed discovery
into a single consistent API and user experience. Editor has been a [long-standing feature request](https://github.com/WordPress/gutenberg/issues/22582).
A GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress.
The editor improves the process and experience of creating new content, making writing
rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes,
custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
experiment that integrates this and other image editing features in a [“Media Editor](https://github.com/WordPress/gutenberg/issues/73771)
[Modal”](https://github.com/WordPress/gutenberg/issues/73771) is ready for testing
and feedback.

## What is it?

The Media Editor Modal replaces the existing inline cropping tool in the Block Editor.
The modal pattern keeps the familiar Crop button entry point, and brings freeform
and aspect-ratio cropping, flip, fine-grained and snap rotation, and metadata editing
into one dedicated workflow.

Under the hood, the modal consumes a coreCore Core is the set of software required
to run WordPress. The Core Development Team builds WordPress. collection custom 
tools and components that will eventually live in a WordPress package. This will
remove the reliance on third-party cropping libraries.

## Why the change?

Image cropping in the Block Editor hasn’t changed much since its [introduction](https://github.com/WordPress/gutenberg/pull/21024).
The existing inline image cropper is built on top of the [react-easy-crop](https://github.com/ValentinH/react-easy-crop)
library. This implementation has a couple of constraints:

 * it’s limited by what’s achievable in the editor canvas and block toolbar, and
 * the library itself has a narrow set of features.

Why build our own library? Well-maintained, open sourceOpen Source Open Source denotes
software for which the original source code is made freely available and may be 
redistributed and modified. Open Source **must be** delivered via a licensing model,
see GPL. alternatives that do most of what users expect are few and far between.
Furthermore, there’s a general preference for a WordPress-native surface that:

 * has all the features we want “out of the box” such as aspect ratios, freeform
   cropping handles, intuitive zooming, flip and rotation,
 * includes all the usability features we’d expect such as touch and keyboard support,
   and
 * is extensibleExtensible This is the ability to add additional functionality to
   the code. Plugins extend the WordPress core software. in ways idiomatic to the
   WordPress ecosystem.

There was an attempt to build a custom, [editor-first cropper component](https://github.com/WordPress/gutenberg/pull/63335),
but it was abandoned. Rather than developing separate, one-off flows across blocks,
the Media Editor Modal aims to provide a consistent foundation for both a [new Media Library experience](https://github.com/WordPress/gutenberg/issues/55238)
and various [editor contexts](https://github.com/WordPress/gutenberg/issues/72734),
and also serve as platform for building more sophisticated experiences later.

## How to test

~If you’re familiar with the [Gutenberg plugin](https://github.com/WordPress/gutenberg)
development environment, you can check out trunktrunk A directory in Subversion 
containing the latest development code in preparation for the next major release
cycle. If you are running "trunk", then you are on the latest revision. right now
and enable the Media Modal experiment from the experiments page at `/wp-admin/admin.
php?page=experiments-wp-admin`~

**Update**: [#78653](https://github.com/WordPress/gutenberg/pull/78653) merged, 
which makes the modal the default experience. No requirement to enable any experiment.

The quickest way to test is via Playground. Here’s a link that loads up Playground
with Gutenberg Trunk and the Media Editor Modal active:

[Test the Media Editor Modal in Playground](https://playground.wordpress.net/?gutenberg-branch=trunk#ewoJIiRzY2hlbWEiOiAiaHR0cHM6Ly9wbGF5Z3JvdW5kLndvcmRwcmVzcy5uZXQvYmx1ZXByaW50LXNjaGVtYS5qc29uIiwKCSJwbHVnaW5zIjogW10sCgkic3RlcHMiOiBbCgkJewoJCQkic3RlcCI6ICJta2RpciIsCgkJCSJwYXRoIjogIi90bXAvZ3V0ZW5iZXJnIgoJCX0sCgkJewoJCQkic3RlcCI6ICJ3cml0ZUZpbGUiLAoJCQkicGF0aCI6ICIvdG1wL2d1dGVuYmVyZy9hcnRpZmFjdC56aXAiLAoJCQkiZGF0YSI6IHsKCQkJCSJyZXNvdXJjZSI6ICJ1cmwiLAoJCQkJInVybCI6ICIvcGx1Z2luLXByb3h5LnBocD9vcmc9V29yZFByZXNzJnJlcG89Z3V0ZW5iZXJnJndvcmtmbG93PUJ1aWxkJTIwR3V0ZW5iZXJnJTIwUGx1Z2luJTIwWmlwJmFydGlmYWN0PWd1dGVuYmVyZy1wbHVnaW4mYnJhbmNoPXRydW5rIiwKCQkJCSJjYXB0aW9uIjogIkRvd25sb2FkaW5nIEd1dGVuYmVyZyBicmFuY2ggdHJ1bmsiCgkJCX0KCQl9LAoJCXsKCQkJInN0ZXAiOiAidW56aXAiLAoJCQkiemlwUGF0aCI6ICIvdG1wL2d1dGVuYmVyZy9hcnRpZmFjdC56aXAiLAoJCQkiZXh0cmFjdFRvUGF0aCI6ICIvdG1wL2d1dGVuYmVyZyIKCQl9LAoJCXsKCQkJInN0ZXAiOiAiaW5zdGFsbFBsdWdpbiIsCgkJCSJwbHVnaW5EYXRhIjogewoJCQkJInJlc291cmNlIjogInZmcyIsCgkJCQkicGF0aCI6ICIvdG1wL2d1dGVuYmVyZy9ndXRlbmJlcmcuemlwIgoJCQl9CgkJfSwKCQl7CgkJCSJzdGVwIjogIndyaXRlRmlsZSIsCgkJCSJwYXRoIjogIi90bXAvd2MtY2hpY2xhbmEtMjAxNy1zd2FnLmpwZWciLAoJCQkiZGF0YSI6IHsKCQkJCSJyZXNvdXJjZSI6ICJ1cmwiLAoJCQkJInVybCI6ICJodHRwczovL3BkLncub3JnLzIwMjEvMTIvODc4NjFiMWNiNWJkNjVlMTUuNjczMjkxMDcuanBlZyIKCQkJfQoJCX0sCgkJewoJCQkic3RlcCI6ICJydW5QSFAiLAoJCQkiY29kZSI6ICI8P3BocFxucmVxdWlyZSAnL3dvcmRwcmVzcy93cC1sb2FkLnBocCc7XG5yZXF1aXJlX29uY2UgQUJTUEFUSCAuICd3cC1hZG1pbi9pbmNsdWRlcy9maWxlLnBocCc7XG5yZXF1aXJlX29uY2UgQUJTUEFUSCAuICd3cC1hZG1pbi9pbmNsdWRlcy9tZWRpYS5waHAnO1xucmVxdWlyZV9vbmNlIEFCU1BBVEggLiAnd3AtYWRtaW4vaW5jbHVkZXMvaW1hZ2UucGhwJztcblxuJGV4cGVyaW1lbnRzID0gKGFycmF5KSBnZXRfb3B0aW9uKCAnZ3V0ZW5iZXJnLWV4cGVyaW1lbnRzJywgYXJyYXkoKSApO1xuJGV4cGVyaW1lbnRzWydndXRlbmJlcmctbWVkaWEtZWRpdG9yLW1vZGFsJ10gPSB0cnVlO1xudXBkYXRlX29wdGlvbiggJ2d1dGVuYmVyZy1leHBlcmltZW50cycsICRleHBlcmltZW50cyApO1xuXG4kaW1hZ2VfcGF0aCA9ICcvdG1wL3djLWNoaWNsYW5hLTIwMTctc3dhZy5qcGVnJztcbiRhbHQgPSAnQ0MwIGxpY2Vuc2VkIHBob3RvIGJ5IFBhYmxvIE1vcmF0aW5vcyBmcm9tIHRoZSBXb3JkUHJlc3MgUGhvdG8gRGlyZWN0b3J5OiBodHRwczovL3dvcmRwcmVzcy5vcmcvcGhvdG9zL3Bob3RvLzg3ODYxYjFjYjUnO1xuXG4kYXR0YWNobWVudF9pZCA9IG1lZGlhX2hhbmRsZV9zaWRlbG9hZChcblx0YXJyYXkoXG5cdFx0J25hbWUnID0+ICd3Yy1jaGljbGFuYS0yMDE3LXN3YWcuanBlZycsXG5cdFx0J3RtcF9uYW1lJyA9PiAkaW1hZ2VfcGF0aCxcblx0KSxcblx0MCxcblx0J01lZGlhIEVkaXRvciBNb2RhbCdcbik7XG5cbmlmICggaXNfd3BfZXJyb3IoICRhdHRhY2htZW50X2lkICkgKSB7XG5cdHRocm93IG5ldyBFeGNlcHRpb24oICRhdHRhY2htZW50X2lkLT5nZXRfZXJyb3JfbWVzc2FnZSgpICk7XG59XG5cbnVwZGF0ZV9wb3N0X21ldGEoICRhdHRhY2htZW50X2lkLCAnX3dwX2F0dGFjaG1lbnRfaW1hZ2VfYWx0JywgJGFsdCApO1xuXG4kaW1hZ2Vfc3JjID0gd3BfZ2V0X2F0dGFjaG1lbnRfaW1hZ2Vfc3JjKCAkYXR0YWNobWVudF9pZCwgJ2xhcmdlJyApO1xuJGltYWdlX3VybCA9ICRpbWFnZV9zcmMgPyAkaW1hZ2Vfc3JjWzBdIDogd3BfZ2V0X2F0dGFjaG1lbnRfdXJsKCAkYXR0YWNobWVudF9pZCApO1xuXG4kcG9zdF9pZCA9IDEyMzQ7XG4kcG9zdF9jb250ZW50ID0gc3ByaW50Zihcblx0JzwhLS0gd3A6cGFyYWdyYXBoIC0tPjxwPkNsaWNrIG9uIHRoZSBpbWFnZSBibG9jayBhbmQgdGhlbiBvbiB0aGUgY3JvcCBpY29uIGluIHRoZSBibG9jayB0b29sYmFyIHRvIG9wZW4gdGhlIG1vZGFsLjwvcD48IS0tIC93cDpwYXJhZ3JhcGggLS0+PCEtLSB3cDppbWFnZSB7XCJpZFwiOiUxJGQsXCJzaXplU2x1Z1wiOlwibGFyZ2VcIixcImxpbmtEZXN0aW5hdGlvblwiOlwibm9uZVwifSAtLT48ZmlndXJlIGNsYXNzPVwid3AtYmxvY2staW1hZ2Ugc2l6ZS1sYXJnZVwiPjxpbWcgc3JjPVwiJTIkc1wiIGFsdD1cIiUzJHNcIiBjbGFzcz1cIndwLWltYWdlLSUxJGRcIi8+PC9maWd1cmU+PCEtLSAvd3A6aW1hZ2UgLS0+Jyxcblx0JGF0dGFjaG1lbnRfaWQsXG5cdGVzY191cmwoICRpbWFnZV91cmwgKSxcblx0ZXNjX2F0dHIoICRhbHQgKVxuKTtcblxud3BfaW5zZXJ0X3Bvc3QoXG5cdGFycmF5KFxuXHRcdCdpbXBvcnRfaWQnID0+ICRwb3N0X2lkLFxuXHRcdCdwb3N0X3RpdGxlJyA9PiAnTWVkaWEgRWRpdG9yIE1vZGFsJyxcblx0XHQncG9zdF9zdGF0dXMnID0+ICdwdWJsaXNoJyxcblx0XHQncG9zdF9hdXRob3InID0+IDEsXG5cdFx0J3Bvc3RfY29udGVudCcgPT4gJHBvc3RfY29udGVudCxcblx0KSxcblx0dHJ1ZVxuKTtcbiIKCQl9CgldLAoJInByZWZlcnJlZFZlcnNpb25zIjogewoJCSJwaHAiOiAiOC4zIiwKCQkid3AiOiAibGF0ZXN0IgoJfSwKCSJmZWF0dXJlcyI6IHt9LAoJImxhbmRpbmdQYWdlIjogIi93cC1hZG1pbi9wb3N0LnBocD9wb3N0PTEyMzQmYWN0aW9uPWVkaXQiLAoJImxvZ2luIjogdHJ1ZQp9)

### Suggested testing flows

The steps are provided just in case you need structure. Don’t feel any need to follow
any or all of them._ _

_The important question is whether the modal is solid enough as a replacement for
the Image block crop flow, and whether you notice any bugs, UXUX User experience
gaps or unexpected behaviors._

#### Basic crop flow

 1. Open the modal from an Image block.
 2. Resize the crop area.
 3. Pan and zoom the image.
 4. Rotate or flip the image.
 5. Save.
 6. Confirm the block updates to use the edited image.

#### Details editing

 1. In a saved post with a title, upload or insert an image.
 2. Open the modal from the Image block.
 3. Switch to the **Details** tab.
 4. Confirm Author and Attached to fields are populated with your author handle and
    the current post’s title.
 5. Update alt text and caption.
 6. Save.
 7. Confirm the media item updates.
 8. Confirm the Image block updates when its existing alt/caption values were empty
    or matched the original media values.

#### Existing custom block values

 1. Add an Image block.
 2. Manually enter custom alt text or a custom caption in the block.
 3. Open the media editor modal.
 4. Change the attachment’s alt text or caption.
 5. Save.
 6. Confirm custom block-level values are not unexpectedly overwritten.

#### Keyboard

 1. Open the modal.
 2. Use Tab to move through the crop area, crop handles, toolbar controls, sidebarSidebar
    A sidebar in WordPress is referred to a widget-ready area used by WordPress themes
    to display information that is not a part of the main content. It is not always
    a vertical column on the side. It can be a horizontal rectangle below or above 
    the content area, footer, header, or any where in the theme. controls, Save, Cancel,
    and Close.
 3. Use arrow keys to move or resize the crop area.
 4. Confirm focus is visible and does not get lost.
 5. Try undo/redo with keyboard shortcuts.
 6. Confirm Escape behaves as expected when there are unsaved changes.

#### **Touch gesture**s

 1. On a touch device, open the modal from an Image block.
 2. Test drag panning, pinch zoom, and crop area handle dragging for responsiveness
    and smoothness.
 3. Ensure toolbar actions like rotate, flip, undo, redo, and reset are tappable.

## Sharing your feedback

Comments on this post are a great way to share feedback, but if you’d like to jump
into Gutenberg feel free to leave feedback on [this tracking issue](https://github.com/WordPress/gutenberg/issues/73771)
as it’s the main one covering current tasks for the experimental modal. We’d love
to know for example:

 * Did the modal open where you expected it to?
 * Was cropping understandable without extra instruction?
 * Did anything feel slower, confusing, or broken?
 * Did the image tools, including Save and Cancel behave as you’d expect?

## Out of scope

The goal is to make the basic crop/edit workflow solid first, not to ship every 
image editing feature. Some related work is still being explored separately, for
example:

 * Manual pixel crop controls.
 * Restoring original image.
 * Improving undo/redo history states.
 * Broader image editor extensibility for image filterFilter Filters are one of 
   the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
   They provide a way for functions to modify data of other functions. They are 
   the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
   manner, and should never have side effects such as affecting global variables
   and output. and/or AI integration options.

Thank you for making it this far, and thanks in advance for testing.

Props to [@andrewserong](https://profiles.wordpress.org/andrewserong/) and [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)
for helping to write this post.

[#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/),
[#media](https://make.wordpress.org/core/tag/media/), [#media-modal](https://make.wordpress.org/core/tag/media-modal/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2026/05/21/media-editor-modal-call-for-testing/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2026/05/21/media-editor-modal-call-for-testing/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2026/05/21/media-editor-modal-call-for-testing/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2026/05/21/media-editor-modal-call-for-testing/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2026/05/21/media-editor-modal-call-for-testing/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2026/05/21/media-editor-modal-call-for-testing/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/d72022082a55c095c92407c901fda1fa5502ce45e7a5ec7740c2576760c4fdd3?
     s=32&d=mm&r=g)
 2.   [Nikunj Hatkar](https://profiles.wordpress.org/nikunj8866/)  4:33 am _on_ May
     22, 2026
 3.  +make.wordpress.org/test/
 4.  ![](https://secure.gravatar.com/avatar/a556f0c812162ab6f10fc8748912889c4b1135aafaa4452badcf5b733bb1f91d?
     s=32&d=mm&r=g)
 5.   [David Perez](https://profiles.wordpress.org/davidperez/)  6:37 am _on_ May 23,
     2026
 6.  Hello!
      Nice initiative! Where is the editor? I don’t find it. Does it takes the
     image sizes already registered in WordPress?
 7.   * ![](https://secure.gravatar.com/avatar/a556f0c812162ab6f10fc8748912889c4b1135aafaa4452badcf5b733bb1f91d?
        s=32&d=mm&r=g)
      *  [David Perez](https://profiles.wordpress.org/davidperez/)  6:39 am _on_ May
        23, 2026
      * I could find it. I don’t see the image sizes. That would be necessary to implement
        the different crops defined in WordPress.
      * ![](https://secure.gravatar.com/avatar/b7a9f6707da61f437f0ca8c7602fb4a49e842879f29b99dc98a629d48e044c28?
        s=32&d=mm&r=g)
      *  [ramonopoly](https://profiles.wordpress.org/ramonopoly/)  3:09 am _on_ May
        24, 2026
      * > I don’t see the image sizes
      * Thanks for comment. Could you elaborate on your expectations?
      * Do you mean whether the crop operation in the Media Editor Modal would apply
        to WordPress’s automatically-generated image subsizes (thumbnail, medium, large,
        etc.)?
      * The answer is “no” – it works in the same way as the current Image blockBlock
        Block is the abstract term used to describe units of markup that, composed 
        together, form the content or layout of a webpage using the WordPress editor.
        The idea combines concepts of what in the past may have achieved with shortcodes,
        custom HTML, and embed discovery into a single consistent API and user experience.
        cropper.
      * This and the current Image block cropper modify the specific instance being
        edited in the block, but do not retroactively regenerate all the registered
        subsizes. The crop is applied to what’s displayed in the specific block context.
        In other words, it’s Block-level, not Attachment-level.
      * I think it would create regressions, and be unexpected in the editor context.
        It’s probably more appropriate for a Media Library context, which is a topic
        for later.
      * If I’ve misunderstood, or if you have a concrete idea on a feature requestfeature
        request A feature request should generally begin the process in the ideas forum,
        on a mailing list, as a plugin, or brought to the attention of the core team,
        such as through scope meetings held for each major release. Unsolicited tickets
        of this variety are typically, therefore, discouraged., it’d be helpful to 
        have them recorded in an issue on the GutenbergGutenberg The Gutenberg project
        is the new Editor Interface for WordPress. The editor improves the process 
        and experience of creating new content, making writing rich content much simpler.
        It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
         
        [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) repo:
      * [https://github.com/WordPress/gutenberg/issues/new/choose](https://github.com/WordPress/gutenberg/issues/new/choose)
      * Thank you!
 8.  ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
     s=32&d=mm&r=g)
 9.   [annezazu](https://profiles.wordpress.org/annezazu/)  9:25 pm _on_ May 27, 2026
 10. Thanks so much for this great call for testing! I gave this a go and have a recording
     here:
 11. [https://cloudup.com/cbRCHpfb4bQ](https://cloudup.com/cbRCHpfb4bQ)
 12. A few notes:
 13.  * The controls at the bottom of the image feel off centered almost.
      * The controls on the right side don’t feel well organized.
      * The zoom control numbers don’t make sense to me/feel broken with the partial
        numbers.
 14. Overall, I think the design and IA can be greatly improved. For example, I think
     the current fine rotation control takes up a ton of space when it may not be the
     most commonly used. I’d rather see that control require a step to engage with 
     it and open up, with the other controls moving out of the way.
 15.  * ![](https://secure.gravatar.com/avatar/b7a9f6707da61f437f0ca8c7602fb4a49e842879f29b99dc98a629d48e044c28?
        s=32&d=mm&r=g)
      *  [ramonopoly](https://profiles.wordpress.org/ramonopoly/)  10:53 pm _on_ May
        27, 2026
      * Thanks for testing, [@annezazu](https://profiles.wordpress.org/annezazu/)
      * We’re currently doing a round of review and polish with designers, and trying
        out a few things. We’ll take this on board as we iterative. Cheers!
      * Some thoughts:
      * > The zoom control numbers don’t make sense to me/feel broken with the partial
        > numbers.
      * This is a float that needs rounding I’d say. I’ll take a look. Should be an
        easy win.
      * > The controls on the right side don’t feel well organized.
      * It is a somewhat arbitrary stack. I’m not sure there’s an objective approach
        here. I think it probably needs more spacing. Was there something specific 
        you had in mind?
      * > The controls at the bottom of the image feel off centered almost.
      * We’re currently looking at how these tools are laid out in [https://github.com/WordPress/gutenberg/pull/78708](https://github.com/WordPress/gutenberg/pull/78708)
      * > I’d rather see that control require a step to engage with it and open up,
        > with the other controls moving out of the way.
      * The progressive disclosure idea for the rotation control is interesting.
      * The tradeoff is discoverability vs. initial noise. I’d like to see more feedback
        on whether users actually reach for fine rotation frequently before committing
        to hiding it behind an extra step, but it’s definitely worth exploring as a
        follow-up iteration.
      * Thank you!
         - ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
           s=32&d=mm&r=g)
         -  [annezazu](https://profiles.wordpress.org/annezazu/)  12:02 am _on_ May
           28, 2026
         - > It is a somewhat arbitrary stack. I’m not sure there’s an objective approach
           > here. I think it probably needs more spacing. Was there something specific
           > you had in mind?
         - Here’s a subtle iteration that moves around the right sidebarSidebar A sidebar
           in WordPress is referred to a widget-ready area used by WordPress themes
           to display information that is not a part of the main content. It is not
           always a vertical column on the side. It can be a horizontal rectangle below
           or above the content area, footer, header, or any where in the theme. items
           and adds a heading as well as hides the fine tuning behind a button:
         - [⌊Screenshot 2026-05-27 at 5.00.26 PM⌉⌊Screenshot 2026-05-27 at 5.00.26 PM⌉[
         - [⌊Screenshot 2026-05-27 at 5.00.32 PM⌉⌊Screenshot 2026-05-27 at 5.00.32 PM⌉[
         - I think it just lands a bit better in this order and approach. I found when
           I first opened the editor, I accidentally changed the values just by hovering
           over the fine control. I also changed the zoom slider to just show the same
           as the percentage. I think that makes a bit more sense but again curious
           what design thinks.
            * ![](https://secure.gravatar.com/avatar/b7a9f6707da61f437f0ca8c7602fb4a49e842879f29b99dc98a629d48e044c28?
              s=32&d=mm&r=g)
            *  [ramonopoly](https://profiles.wordpress.org/ramonopoly/)  12:48 am _on_
              May 28, 2026
            * Thanks for building and sharing those screenshots. I like the angle icon!
              Keeping [@jameskoster](https://profiles.wordpress.org/jameskoster/) in
              the loopLoop The Loop is PHP code used by WordPress to display posts.
              Using The Loop, WordPress processes each post to be displayed on the 
              current page, and formats it according to how it matches specified criteria
              within The Loop tags. Any HTML or PHP code in the Loop will be processed
              on each post. [https://codex.wordpress.org/The_Loop](https://codex.wordpress.org/The_Loop)
              too.

Comments are closed.

# Post navigation

[← What’s new in Gutenberg 23.2? (21 May)](https://make.wordpress.org/core/2026/05/21/whats-new-in-gutenberg-23-2-21-may/)

[PHP support clarification, spring 2026 edition →](https://make.wordpress.org/core/2026/05/22/php-support-clarification-2026/)