Skip to content

WordPress 7.1 Iteration: Media Editor Modal task tracking #73771

Closed
2 of 2 issues completed
Closed

Description

@andrewserong

Add a Gutenberg-powered media editor that's intended to eventually replace cropping tools and the core media editor screen with a more modern and extensible interface.

The first stage (now in trunk) is to replace the inline cropping tool used by the Image block with a full media editor modal.

When complete, we'll be able to close out these issues:

Also, to keep in mind: ensuring that the media features are extensible, especially via the AI plugin:

Current state:

Image

Scope

PRs (to help us keep track)

Feedback to explore

  • Should we hide the fine-grained rotation behind a toggle button?
  • Try moving some (or all) of the transform controls above the image being edited (needs design)
  • Where do we put the Keyboard modal toggle button?

Done

Tasks that have been completed (kept for posterity)
  • Fix loading of the "Attached to" entity
  • Polish "Details" fields:
    • The "Date added" field can unexpectedly wrap on datetime strings like May 12, 2026 6:44 am
    • If the post hasn't yet been saved, the Attached to field says "Auto Draft" (that's consistent with core behaviour)
    • If the post doesn't have a title, the Attached to field displays the id number of the post (fixed to display (no title) for consistency with core)
  • Update the previous "Media Editor" experiment if/when this experiment feels solid
  • Try out a zoom area component that controls the zoom of the camera/world without adjusting the crop area. Similarly, to allow panning the camera/world separately from moving the crop area. Essentially allowing a way to browse the area a bit like we might in Figma/Photoshop/Affinity. (Explored, but scaled it back to adding auto-pan behaviour for now)
  • Or, alternately, at least make it easier for folks to expand the current crop area beyond the current level of zoom (without this, it's easy to feel stuck and unable to expand a small crop area back to a larger size)
  • Add undo/redo behaviour
    • Add basic undo/redo for the cropper itself
    • Wire up controls that live outside of the cropper and include them in undo/redo stacks (e.g. aspect ratio select, freeform crop toggle)
  • Should save and cancel should be in the bottom right?
  • Prevent undo/redo in the middle of a gesture. Attempt 1. Attempt 2.
  • If a user updates Caption and Alt Text but has never entered those details manually in the image block, then updating them in the cropping tool should propagate it into the Image block

To-do

Activity

  1. added
    [Feature] MediaAnything that impacts the experience of managing media
    [Type] IterationScoped iteration of an effort from a tracking issue or overview issue ideally for a major release.
    on Dec 4, 2025
  2. self-assigned this
    on Dec 5, 2025
  3. moved this to 📋 Iteration/Tracking Issues in WordPress 7.0 Editor Taskson Jan 6, 2026
  4. andrewserong commented on Jan 16, 2026

    @andrewserong
    ContributorAuthor

    Update:

  5. eric-michel commented on Feb 1, 2026

    @eric-michel

    I'm not sure if this is an appropriate place to request any new features for media editing, but adding a media-level focal point selector (similar to the cover block) that gives a media item a global level focal point (which could be overridden in an individual cover block) would be incredibly helpful. Having this focal point output in some way via wp_get_attachment_image would also be critical.

    We currently use custom fields to select images on a regular basis (in ACF, for instance) and often will use object-fit: cover in whatever custom implementation we're doing at the time. Having the ability to add a focal point natively would enhance what we can do a lot.

    We're currently using this excellent plugin, but this really feels like a core feature that should exist anytime an image is set to object-fit: cover or set as a background image.

  6. changed the title [-]Media Editor in WordPress 7.0[/-] [+]Media Editor in WordPress 7.1[/+] on Feb 2, 2026
  7. moved this from 📋 Iteration/Tracking Issues to 🦵 Punted to 7.1 in WordPress 7.0 Editor Taskson Feb 2, 2026
  8. andrewserong commented on Feb 2, 2026

    @andrewserong
    ContributorAuthor

    Update: while work is progressing pretty well on the media editor (see tracking issue and latest WIP PR exploring cropping tools), there are still quite a few features left to implement and not much time before the 7.0 feature freeze (beta 1). Due to the complexity of tasks remaining, I'm going to punt this to WP 7.1 to allow more time to explore key features like extensibility, and to give more time for adequate rounds of testing and iteration before proposing introducing in core.

    I intend to keep working on this, but it will be a little bit on the back-burner over the next couple of weeks as I help out with higher priority 7.0 tasks for this release. I've updated the issue description.


    I'm not sure if this is an appropriate place to request any new features for media editing, but adding a media-level focal point selector

    Thanks for raising it @eric-michel! If you're keen to see that feature as part of a new media editor / media library, a fresh issue would be a good place to suggest it, as that way folks can dig into implementation details a bit better than on tracking / iteration issues like this one.

    At first glance that sounds like a really useful feature! For my part, my main focus on these kinds of media tasks (both the media editor and media library modal) is to attempt to build a DataViews/DataForms-powered representation of the media library that seeks to have parity with the existing media library in core. So the first goal will be to build out what currently works, and then we'd be able to explore adding additional features (including setting a media-level focal point, etc) once we've got feature parity in place.

  9. eric-michel commented on Feb 3, 2026

    @eric-michel

    Got it! Thanks @andrewserong! I'll make a new issue.

  10. changed the title [-]Media Editor in WordPress 7.1[/-] [+]Media Editor task tracking[/+] on Apr 1, 2026
  11. andrewserong commented on Apr 2, 2026

    @andrewserong
    ContributorAuthor

    Update: with folks beginning to make plans for WordPress 7.1 I've removed 7.1 from the title of this tracking issue. Speaking for myself, I'm intending to focus more on helping out with the client-side media processing work (primarily with reviews) alongside some of the work recently flagged in:

    As such, I think we should drop aiming to get this feature in for any particular WP release at this stage, and instead chip away at it on the side. (It's still a feature I'd love to see land, but personally I'll likely only have time to chip away at it on the side)

  12. 51 remaining items

  13. ramonjd commented on Jul 1, 2026

    @ramonjd
    Member

    In principle I agree (simplifying to reduce cognitive load in general), but I think why I'm stuck on this particular feature is that it's one I personally use quite frequently. So I don't want to arbitrarily be a blocker, but because I use it and like it, that's why I'm advocating for it.

    Let's hold off on this until we clarify extensibility points, which is a sizeable and important feature. Accessible/advanced controls mentioned above is another one.

    7.2 or beyond is a reasonable target to build on a stable base.

    We'll also get instructive feedback during Beta (coming very soon), which we can factor in.

  14. moved this to 📋 Iteration/Tracking Issues in WordPress 7.1 Editor Taskson Jul 4, 2026
  15. joedolson commented on Jul 7, 2026

    @joedolson
    Contributor

    Accessibility issues in the editor:

    • Screen reader feedback from crop manipulation should prioritize the value you're currently changing. E.g., when adjusting crop boundaries using the keyboard and a screen reader, the adjustment made is reported as "Zoom 106%, Crop 100% by 95%". This is confusing, when what you're actually adjusting is the crop position. Similarly, if you're adjusting rotation, the rotation should be reported first.
    • The quantity of adjustment needs to indicate which values have changed - is the height at 95%, or is the width at 95%? How many pixels has that actually shifted?
    • The degree of rotation should probably indicate direction of rotation. While positive and negative values traditionally indicate clockwise and counterclockwise, not all users will know that, and it doesn't match the labeling of the Rotate buttons, which both use positive values.
    • Labeling: "Resize [position] corner" seems like it should actually be "Resize from [position] corner". Technically, you're repositioning the corner, or resizing with relation to that corner.
    • When media editor is open, the non-modal regions should be marked as inert; it is currently marked as aria-hidden, which leaves it keyboard accessible.
    • The alt text field in the Details panel should have the same alternative text information context found in all other media contexts.

    Overall, the screen reader feedback and experience is fairly good.

  16. ramonjd commented on Jul 7, 2026

    @ramonjd
    Member

    Thanks for testing @joedolson

    I can get a PR up to address your points soon. Appreciate the feedback.

  17. ramonjd commented on Jul 7, 2026

    @ramonjd
    Member

    I can get a PR up to address your points soon.

    When media editor is open, the non-modal regions should be marked as inert; it is currently marked as aria-hidden, which leaves it keyboard accessible.

    This is looking like a broader components change. From what I can see, the modalize() helper that handles this lives in @wordpress/components Modal, and is shared by every modal. I reckon that's better for a separate PR.

  18. ramonjd commented on Jul 7, 2026

    @ramonjd
    Member

    I reckon that's better for a separate

    I'm not confident this is right, but threw it up anyway

  19. changed the title [-]Media Editor Modal task tracking[/-] [+]WordPress 7.1 Iteration: Media Editor Modal task tracking[/+] on Jul 17, 2026
  20. ramonjd commented on Jul 17, 2026

    @ramonjd
    Member

    Heads up: this issue will be closed after 7.1 ships.

    Planning next steps to be done over in:

  21. t-hamano commented on Aug 12, 2026

    @t-hamano
    Contributor

    Since the 7.1 release is next week, can we close this issue and create a tracking issue for 7.2 if needed?

  22. andrewserong commented on Aug 12, 2026

    @andrewserong
    ContributorAuthor

    Since the 7.1 release is next week, can we close this issue and create a tracking issue for 7.2 if needed?

    Yep! The 7.2 tracking issue is already up over in #80389 so let's close this out now.

  23. moved this from 📋 Iteration/Tracking Issues to ✅ Done in WordPress 7.1 Editor Taskson Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

[Feature] MediaAnything that impacts the experience of managing media[Type] IterationScoped iteration of an effort from a tracking issue or overview issue ideally for a major release.

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions