Skip to content

Client Side Media iteration for WordPress 7.2 and beyond #80159

Open
8 of 25 issues completed
Open

Description

@adamsilverstein

Top Tickets for WordPress 7.2

Nice to have in 7.2

Bug fixes/refinements for 7.2

Goals for WordPress 7.3 or later

New Capabilities

Infrastructure

Image format support

What shipped during the 7.1 development cycle

The 7.1 cycle closed out most of the goals from #76756, including:

Future plans

Down the road, the roadmap also includes audio transcoding, image editing, BlurHash placeholders, per-size format optimization, and saliency-based cropping.
If there is something you would like to see on the client side media roadmap, please leave a comment.

History

Previous tracking issues:

Activity

  1. added
    [Type] IterationScoped iteration of an effort from a tracking issue or overview issue ideally for a major release.
    on Jul 13, 2026
  2. 10 remaining items

  3. adamsilverstein commented on Aug 25, 2026

    @adamsilverstein
    MemberAuthor

    I was going through open issues in https://github.com/swissspidy/media-experiments and there might be some relevant items in there for this iteration.

    Thanks for the links @swissspidy - I created some additional bug and enhancement issues based on those and linked back to your repo as reference material.

  4. gregbenz commented on Sep 7, 2026

    @gregbenz

    The planned upload and editing work looks like a strong foundation for broader HDR JPEG support. Could we define end-to-end acceptance criteria for JPEG gain-map preservation, identifying which workflows are covered in 7.2 and which need follow-up?

    The main questions I have are: Does HDR processing work across Gutenberg, Media Library, media modals, and third-party editors such as Elementor? What (if any) integration will third-party editors need to implement?

    Some of this already has implementation and tests underway. The goal would be to connect that work and make remaining coverage and limitations explicit, rather than assume everything must ship in 7.2. Would a dedicated HDR workflow/acceptance issue linked here be useful?

  5. adamsilverstein commented on Sep 30, 2026

    @adamsilverstein
    MemberAuthor

    Client Side Media Update: September 30, 2026

    Claude helped me pull this together from the sub-issues and their PRs; the priorities are mine:

    Summary

    Client-side media processing shipped in WordPress 7.1 for the block editor, and the 7.2 cycle has been about two things: bringing the same pipeline to the rest of the admin (the Media Library grid, Media > Add New, and the editor's media modal), and hardening the package based on what real uploads turned up once 7.1 was in the wild. WordPress 7.2 Beta 1 lands October 20-22, so there are about three weeks left to get the remaining 7.2 items reviewed and merged.

    The headline outside of the code is the progress on the Document-Isolation-Policy (DIP) standard. DIP is what lets WordPress enable SharedArrayBuffer for wasm-vips without breaking third-party embeds, and it has been Chromium-only so far. Since WordPress adopted it, Mozilla's position moved to positive, and on September 26 WebKit confirmed their portability concerns are resolved, leaving venue (upstreaming into HTML and Fetch) as the only remaining objection. To help move that along, WICG/document-isolation-policy#8 asks for the upstreaming work to start, WebKit bug 325516 formally requests an implementation, and DIP has been proposed for Interop 2027. Chrome shipped DIP on desktop in 137 and on Android in 146. This is WordPress helping move the web platform forward, and it is the path to client-side media in Firefox and Safari without a separate plugin.

    Top priorities before Beta 1

    These two are the "Top Tickets for 7.2" from the description, and both could use reviewer attention now:

    Highlights since the 7.1 wrap-up

    Merged Gutenberg PRs since the last update

    Bug fixes and hardening

    Cross-origin isolation

    Animated GIF and video

    7.1.x backports

    Core (wordpress-develop) since the last update

    Committed:

    Open, pairing with Gutenberg work:

    In flight and needing review

    Ready or close to ready for 7.2, in rough priority order:

    Nice to have for 7.2 if reviews line up:

    Tracking for 7.3 or later:

    Open issues without a PR yet: #82034 (external image sideload skips part of the REST attachment path; @sanketio reports the first four items are implemented with tests and ready to open), #82613 (finalize architecture, discussion ongoing with @andrewserong and @swissspidy), #82264 (per-session batch record for upload progress), and #79559 (HDR NCLX/CICP color metadata in AVIF output, blocked upstream in libvips).

    Open questions

    As always, testing and review help is appreciated, especially on wpd #12585 and #82473 before Beta 1. ?

  6. josephfusco commented on Oct 14, 2026

    @josephfusco
    Contributor

    A request for the 7.3 list: measure audio waveform peaks in the browser at upload and store them in attachment metadata, so the Playlist block, the Audio block and plugins stop downloading and decoding the whole file to draw a waveform. Written up in #84712, with #83086 as the fallback for tracks without an attachment and #82035 as the likely seam.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    [Feature] Client Side MediaMedia processing in the browser with WASM[Type] EnhancementA suggestion for improvement.[Type] IterationScoped iteration of an effort from a tracking issue or overview issue ideally for a major release.

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions