Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Text and images are displayed cropped if folder has long name #1758

Closed
engcom-Lima opened this issue Aug 17, 2020 · 1 comment · Fixed by magento/magento2#29633
Closed

Text and images are displayed cropped if folder has long name #1758

engcom-Lima opened this issue Aug 17, 2020 · 1 comment · Fixed by magento/magento2#29633
Assignees
Labels
Priority: P2 Should be fixed as early as possible Progress: done Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround
Projects
Milestone

Comments

@engcom-Lima
Copy link

engcom-Lima commented Aug 17, 2020

Preconditions (*)

  1. Install Magento 2.4-develop with Adobe Stock Integration and IMS
  2. Configured integration in Stores -> Configuration -> Advanced-> System -> Adobe Stock Integration fieldset
  3. Enhanced Media Gallery Enabled

Steps to reproduce (*)

  1. Go to Content -> Media Gallery
  2. Create a folder with long name (for example: TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSSSSSTTTTTTTTTTTTTT)
  3. Select it

Expected result (*)

"We couldn't find any records." text should be displayed without cropping it there is no image. If there is an image, it should also be displayed without cropping.

Actual result (*)

The "We couldn't find any records." text displays cropped. If there is an image, it is also displayed cropped.
Peek 2020-08-17 12-42

@m2-assistant
Copy link

m2-assistant bot commented Aug 17, 2020

Hi @engcom-Lima. Thank you for your report.
To help us process this issue please make sure that you provided sufficient information.

Please, add a comment to assign the issue: @magento I am working on this


@m2-community-project m2-community-project bot added this to Ready for Grooming in Backlog Aug 17, 2020
@Nazar65 Nazar65 self-assigned this Aug 17, 2020
@m2-community-project m2-community-project bot moved this from Ready for Grooming to Dev In Progress in Backlog Aug 17, 2020
@sivaschenko sivaschenko added Priority: P2 Should be fixed as early as possible Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround labels Aug 17, 2020
@sivaschenko sivaschenko added this to the 2.1.0 milestone Aug 17, 2020
Backlog automation moved this from Dev In Progress to Done Aug 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P2 Should be fixed as early as possible Progress: done Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround
Projects
Backlog
  
Done
3 participants