You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Opening a post that has an image still uploading, shows the image as fully ready (undimmed and without a progress bar), only to show the dimming and progress bar a second or so later.
To Reproduce
Steps to reproduce the behavior:
Start a Gutenberg post, add an Image block and select an image from the device to upload
Go back to the post list by tapping the "Back" button, without publishing the post
Quickly enough, tap on the draft to open it again while the image is still uploading
Notice that the image appears fully ready for a small amount of time and then is dimmed and adopts a progress bar as the uploading progresses 💥
Expected behavior
The image should immediately have the dimming and the progress bar upon opening the post so to be no confusion about its state.
Screenshots
See the GIF:
Smartphone (please complete the following information):
Device: Pixel 2 XL
OS: Android 10
Version WPAndroid 14.4-rc-1, gutenberg-mobile v1.23.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Going to close as I'm not able to reproduce as of 24.3. Also related: There are discussions to remove the opacity/process indicator for uploading images as part of #6603.
Describe the bug
Opening a post that has an image still uploading, shows the image as fully ready (undimmed and without a progress bar), only to show the dimming and progress bar a second or so later.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The image should immediately have the dimming and the progress bar upon opening the post so to be no confusion about its state.
Screenshots
See the GIF:
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: