WordPress.org

Make WordPress Core

Opened 14 months ago

Last modified 13 months ago

#51584 new defect (bug)

Publishing a large image post while the image is still uploading allows you to leave and return to a broken image

Reported by: garrett-eclipse Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Media Keywords:
Focuses: ui, administration Cc:

Description

This issue was originally reported by @antpb in #core-media here;
https://wordpress.slack.com/archives/C02SX62S6/p1603135350316800

If you go to the post editor and upload a large image to the image block, then publish/save and leave the screen before it's uploaded you'll return to the post with a broken image.

I'm thinking we should provide a dirty flag while that upload/resize process is underway for large images to flag to users and stop them from leaving the editor before the process completes.

Attachments (1)

40ac89ddf1f68dbfcd69cededf50e547.gif (1.8 MB) - added by garrett-eclipse 14 months ago.
Screen share showing the issue

Download all attachments as: .zip

Change History (9)

@garrett-eclipse
14 months ago

Screen share showing the issue

#1 @garrett-eclipse
14 months ago

One note the images do upload to the library so it's the resize process that's being interrupted it seems.

This ticket was mentioned in Slack in #core-editor by garrett-eclipse. View the logs.


14 months ago

This ticket was mentioned in Slack in #core by garrett-eclipse. View the logs.


14 months ago

This ticket was mentioned in Slack in #core-media by hellofromtonya. View the logs.


14 months ago

#5 @helen
13 months ago

@garrett-eclipse Is this new to trunk? Seems like it's probably existed in the block editor all this time, but want to make sure before changing the version to 5.0 so it doesn't stay on the 5.6 radar.

This ticket was mentioned in Slack in #core by helen. View the logs.


13 months ago

This ticket was mentioned in Slack in #core-media by hellofromtonya. View the logs.


13 months ago

#8 @hellofromTonya
13 months ago

  • Version trunk deleted

In talking with the Media team, this issue does not appear to be a 5.6 regression. The team is currently not sure which version to attribute. Removing it from trunk.

Note: See TracTickets for help on using tickets.