Image block cropping: Sync image size and link destination settings

[andrewserong]

What?

Fixes #82296

This fixes a subtle bug in the Image block when cropping an image:

In the image block's handling of media after a crop is performed, attempt to sync across the selected image size that a user has set for the particular block. So, if a block is set to "medium" or "large" size, then once the crop has been performed and the new attachment refetched, assign that particular image size.

While we're here, also ensure that the new url for the cropped attachment is the one that gets used for a wrapper a tag if the user has selected to have the image block link to the image file.

Why?

Prior to this change, as described in #82296, if you'd selected anything other than full size for the image, then after performing a crop, the image block would revert back to being at full size, but the UI would be stuck on whatever you chose. This change makes the image resolution settings a user selects independent from cropping the image. The cropping modal continues to use the full source image.

Additionally, while testing out #82296, I stumbled across another subtle bug where if you're using the "Link to image file" setting on the image block, then the previous crop would be the image that gets linked to, rather than the full source url of the new crop. It should be the latter, as that's now the "real" attachment.

How?

• In useOpenImageMediaEditorModal add a couple of helper functions to manage pulling in the right url depending on the sizeSlug being used, and using the right url when the image is set to link to the image file or attachment

Testing Instructions

• Add an image to a post or page
• Click the link button button in the block toolbar and set it to "Link to image file"

• In the settings sidebar, set the image to a size other than Full, e.g. Large or Medium
• Open up the cropper for the image
• Crop the image
• In the editor, the image size you selected should still be selected, and the image rendered in the editor should be that size (i.e. the smaller medium or full image, not the full sized image)
• Save the post
• View the post on the site frontend, and it should still be the medium/large image size depending on what you chose
• Click on the image, and it should take you to the full sized version of the cropped image and not the original uncropped attachment

Screenshots or screencast

This shows selecting "Link to image file", a lower image resolution, performing a crop, and the smaller image size (cropped) in the editor and site frontend, with the link on the site frontend going to the full size version of the cropped image:

2026-09-02.15.22.28.mp4

Use of AI Tools

Claude Code (Opus 5)

[github-actions]

🤖 PR meta 🤖

📦 Bundle size

Size Change: +131 B (0%)

Total Size: 8 MB

📦 View Changed

Filename	Size	Change
build/scripts/block-library/index.min.js	371 kB	+131 B (+0.04%)

_{c0a031a Run}

⚡ Performance

Show the results

Client side metrics exclude the server response time.

front-end-block-theme

Metric	731dffc	trunk	% Change
timeToFirstByte	70 ms +6% -12.57%	64.85 ms +6.71% -12.8%	7.94%
largestContentfulPaint	104 ms +11.54% -5.77%	96 ms +12.5% -8.33%	8.33%
lcpMinusTtfb	32.35 ms +25.81% -2.32%	32.7 ms +6.73% -6.88%	-1.07%
wpBeforeTemplate	35.82 ms +5.72% -13.32%	33.82 ms +3.99% -19.4%	5.91%
wpTemplate	27.08 ms +13.18% -2.18%	25.95 ms +5.74% -5.05%	4.35%
wpTotal	64.42 ms +6.01% -10.96%	60.12 ms +5.42% -12.41%	7.15%
wpMemoryUsage	7.54 MB +0% -0%	7.50 MB +0% -0%	0.46%
wpDbQueries	17 +0% -0%	17 +0% -0%	0%

front-end-classic-theme

Metric	731dffc	trunk	% Change
timeToFirstByte	39.2 ms +10.2% -2.55%	49.15 ms +12.82% -5.49%	-20.24%
largestContentfulPaint	80 ms +10% -0%	94 ms +10.64% -2.13%	-14.89%
lcpMinusTtfb	41.35 ms +2.9% -3.26%	45.7 ms +5.14% -1.64%	-9.52%
wpBeforeTemplate	24.41 ms +14.99% -2.05%	24.88 ms +22.35% -3.9%	-1.89%
wpTemplate	11.42 ms +3.85% -2.36%	19.58 ms +5.92% -1.58%	-41.68%
wpTotal	35.95 ms +10.74% -1.72%	45.81 ms +11.66% -5.52%	-21.52%
wpMemoryUsage	5.42 MB +0% -0%	6.12 MB +0% -0%	-11.5%
wpDbQueries	10 +0% -0%	14 +0% -0%	-28.57%

media-processing

Metric	731dffc	trunk	% Change
mediaProcessingJpeg	413.72 ms +1.09% -0.34%	418.08 ms +1.08% -0.78%	-1.04%
mediaProcessingAvif	6398.99 ms +0.44% -0.12%	6425.56 ms +0.55% -0.57%	-0.41%
mediaProcessingJpegToAvif	4567.47 ms +0.17% -0.29%	4584.87 ms +0.28% -0.09%	-0.38%

media-upload

Metric	731dffc	trunk	% Change
jpegUploadProcessing	1713.8 ms +14.23% -15%	1451.07 ms +0.44% -0.59%	18.11%
pngUploadProcessing	218.83 ms +0.42% -6.17%	217.7 ms +3.04% -3.51%	0.52%
largeJpegUploadProcessing	1441.8 ms +0.3% -0.88%	1436.46 ms +0.3% -0.58%	0.37%
multipleImageUploadProcessing	1568.84 ms +2.58% -1.02%	1582.91 ms +1.16% -2.36%	-0.89%

post-editor

Metric	731dffc	trunk	% Change
serverResponse	576.61 ms +3.16% -4.3%	563.13 ms +4.38% -4.59%	2.39%
firstPaint	292.4 ms +14.35% -12.32%	283.31 ms +10.29% -19.31%	3.21%
domContentLoaded	1394.92 ms +2.67% -1.65%	1334.52 ms +1.95% -2.25%	4.53%
loaded	1396.36 ms +2.66% -1.62%	1335.98 ms +1.93% -2.25%	4.52%
firstContentfulPaint	469.2 ms +3.53% -3.69%	440.05 ms +2.57% -11.23%	6.62%
firstBlock	3860.12 ms +1.53% -0.41%	3667.15 ms +2.62% -1.89%	5.26%
type	22.01 ms +18.67% -10.72%	23.95 ms +2.51% -12.99%	-8.1%
typeWithoutInspector	21.61 ms +11.52% -16.52%	21.46 ms +12.02% -16.68%	0.7%
typeWithTopToolbar	26.85 ms +5.29% -13.74%	25.99 ms +11.54% -10.66%	3.31%
typeContainer	9.93 ms +13.6% -13.29%	9.71 ms +5.56% -8.75%	2.27%
focus	87.64 ms +21.59% -7.71%	87.19 ms +12.4% -3.96%	0.52%
firstFocus	213.13 ms +0% -0%	184.32 ms +0% -0%	15.63%
selectAll	635.38 ms +5.5% -0.16%	641.3 ms +0.76% -2.55%	-0.92%
listViewOpen	79.74 ms +7.22% -12.52%	70.72 ms +21.85% -5.53%	12.75%
inserterOpen	25.94 ms +11.53% -10.95%	23.97 ms +14.31% -6.17%	8.22%
inserterHover	4.47 ms +8.95% -20.81%	3.62 ms +6.08% -4.7%	23.48%
inserterSearch	10.07 ms +10.53% -7.15%	9.04 ms +5.86% -10.18%	11.39%
loadPatterns	665.57 ms +4.2% -2.76%	659.5 ms +3.96% -4.27%	0.92%
wpTotal	566.88 ms +3.12% -4.49%	553.1 ms +4.5% -4.7%	2.49%
wpMemoryUsage	13.13 MB +0% -0%	13.10 MB +0% -0%	0.22%
wpDbQueries	53 +1.89% -0%	54 +0% -1.85%	-1.85%

site-editor

Metric	731dffc	trunk	% Change
serverResponse	549.25 ms +1.54% -3.91%	540.44 ms +2.3% -2.49%	1.63%
firstPaint	264.48 ms +13.83% -16.2%	245.35 ms +7.15% -3.08%	7.8%
domContentLoaded	1376.91 ms +0.91% -0.67%	1385.22 ms +2.25% -1.38%	-0.6%
loaded	1378.22 ms +0.89% -0.66%	1386.53 ms +2.23% -1.38%	-0.6%
firstContentfulPaint	436.04 ms +1.74% -2.72%	431.67 ms +1.5% -2.11%	1.01%
firstBlock	4438.29 ms +0.78% -0.33%	4431.2 ms +0.56% -0.52%	0.16%
type	20.59 ms +18.36% -12.53%	21.85 ms +8.42% -16.16%	-5.77%
navigate	97.38 ms +2.04% -3.86%	107.43 ms +6.72% -3.74%	-9.35%
loadPatterns	1368.86 ms +16.06% -8.27%	1453.48 ms +16.55% -11.44%	-5.82%
loadPages	1260.96 ms +14.55% -6.89%	1164.56 ms +10.36% -4%	8.28%
wpTotal	539.81 ms +1.55% -3.97%	531.17 ms +2.24% -2.67%	1.63%
wpMemoryUsage	12.02 MB +0% -0%	11.99 MB +0% -0%	0.3%
wpDbQueries	43 +2.33% -0%	43 +2.33% -0%	0%

_{c0a031a Run}

[Copilot]

🟡 Changes recommended

A failed attachment refetch can leave the size and link attributes inconsistent.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Fixes Image block cropping so selected image sizes and link destinations follow the new attachment.

Changes:

• Derives the selected image size and link URL after cropping.
• Adds unit tests for size preservation, fallbacks, and links.

File summaries

File	Description
use-open-image-media-editor-modal.js	Synchronizes cropped attachment attributes.
use-open-image-media-editor-modal.jsdom.test.js	Tests synchronization behavior.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Balanced

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

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.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org>
Co-authored-by: gregbenz <gregbenz@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[ramonjd]

Kapture.2026-09-02.at.17.09.17.mp4

Confirmed the bug on trunk, and also that this PR ensures the cropped images get the size and href attributes. Tried at all sizes with intermediate crops.

If copilot is happy, then i am!

Thanks for the quick fix

[ramonjd]

as selecting a new image does

Nit. It looks like selecting a new image tries the imageDefaultSize setting before full, not when when the selected size is missing.

Could just remove this bit. No biggie

[andrewserong]

Ah, so it does! Thanks for the eagle eyes here. I've dropped the "as selecting a new image does".

[ramonjd]

Just checking don't we already have fullUrl in sizes.full?.source_url?

[andrewserong]

Oh, good catch, I was totally overthinking this part when I was trying to find errors where things could fail in-between starting the crop and updating the data.

This is much simpler 👍

[adamsilverstein]

@andrewserong - thanks for fixing this. do you think this is worth backporting to 7.1.1, or fine to leave for 7.2? Is this a bug that was newly introduced in 7.1?

[andrewserong]

do you think this is worth backporting to 7.1.1, or fine to leave for 7.2? Is this a bug that was newly introduced in 7.1?

Good question, thanks for the ping! It will be a bug that was newly introduced in 7.1 because the media editor modal was introduced in that release.

In terms of severity, I don't think it's critical to get into 7.1.1 as it's something a user can work around via the UI. But if possible, it'd be good to include it. I've added the Backport label 👍

[adamsilverstein]

This will be included in 7.1.1, see #82383