Cannot undo image resizing

[ellatrix]

Once I have resized an image, there is no way to remove the fixed size to let it be responsive again. I guess I would expect there to be an option responsive/fixed, that automatically switches to fixed if you start resizing.

Similarly, with image resizing enabled, I'm a bit afraid that users will resize an image back to what looks like full-width and then think it's full-width. In reality that won't be the case if the image is displayed in a box that has a different width. I wonder if it might be more interesting to have preset responsive sizes.

[mtias]

This works now.

[aduth]

In what way is this working? It's unclear to me how to remove custom sizing from an image which had been previously resized.

Raised by @bobbingwide

Reopening in case it's still not possible; unsure if the original issue was related specifically to Undo/Redo, but it seems reasonable to me we should want to allow a user to unset the custom size when editing a post at a later date (i.e. when Undo history doesn't apply).

[mtias]

Using alignment buttons can reset the resizing. Might be worth adding a button on the inspector for it. cc @jasmussen

[jasmussen]

It doesn't seem like you can unset the resizing in the classic editor, or at least I couldn't find a way:

That's not to say we can't do better in Gutenberg, we certainly can. Here are some mockups created for a pull request:

In this, you have additional inspector options for images. There are explicit dimension input fields, quick shortcuts to set scaling sizes, and a button to reset the size.

[mtias]

Yes, let's go with that.

[bobbingwide]

I must be missing something here.

1. Joen said he couldn't find a way with the classic editor. Even though the image does not appear to change inside the editor, saving and viewing shows that the image size does get changed. Switch to text view.
2. What does "Let's go with that" mean?

Perhaps you could explain to me what a status of Closed means for this project.

[jasmussen]

@bobbingwide Matías was a bit brief in his comment there. He forgot to suggest the reason for closing, which was to consolidate tickets. Turns out there's already a ticket that touches on this same issue: #4914