Edit Image UX needs improvement

[deepakvijayan]

Bug Report

Description

When editing(scale and crop) an image via "Attachment details". The settings for the selected feature are shown at the end of the popup. This would be fine in the case of smaller images. But for larger images, especially ones in the portrait orientation, these settings are not visible on the screen unless one scrolls down. There seems to be room for UX improvement here.

I think we can keep the settings on the right-hand side of the popup, which would remove the need to scroll down to use them, no matter what the image size is.

Also, I felt this must have been done as such since not all features need a settings section. But can't that be handled by maybe toggling the section altogether? ( if placed on the right that is )

Attaching videos for reference. The video names describe the test cases.

Environment

• WordPress: 6.3-beta4
• PHP: 7.4.12
• Server: Apache/2.4.46 (Unix) OpenSSL/1.0.2u PHP/7.4.12 mod_wsgi/3.5 Python/2.7.13 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1
• Database: mysqli (Server: 5.7.32 / Client: mysqlnd 7.4.12)
• Browser: Chrome 114.0.0.0 (macOS)
• Theme: Twenty Twenty-Three 1.1
• MU-Plugins: None activated
• Plugins:
  • WordPress Beta Tester 3.5.1

Steps to Reproduce

1. Navigate to Media Library
2. Select a large Image to edit(preferably Portrait orientation)
3. Edit Image
4. Click on the "Scale" button
5. Nothing happens
6. Settings are shown at the end of the popup which can only be seen if scrolled.

Expected Results

1. On clicking the "Scale" button, the settings to edit the scale should be visible to the user.

Actual Results

1. Right now "Scale & Crop" settings are only visible if scrolled down(for bigger images).

[joedolson]

Related: #58979

[antpb]

Hi @deepakvijayan in the recent Media Component meeting we discussed this ticket and are thinking that this is now closed with the enhancements in #58979. If you think that this should still be opened feel free to reopen this ticket and let us know what you'd like to see different. As we are reading the ticket in current state we're having trouble knowing how this is different from the other issue that is resolved. Thanks!