magento2
magento2 copied to clipboard
"Uncaught TypeError: Cannot read property 'clientWidth' of undefined" error message appears on New Media Gallery page
Preconditions (*)
- Install Magento with Adobe Stock Integration
- Configured integration in Stores -> Configuration -> Advanced-> System -> Adobe Stock Integration fieldset
Steps to reproduce (*)
- Log in Admin Panel and go to Stores - Configuration - Advanced - System- Media Gallery
- Set Enable Old Media Gallery to No.
- Save Config and clear Magento cache
- Log out from Admin
- Generate small profile for your instance
php bin/magento setup:performance:generate-fixtures setup/performance-toolkit/profiles/ce/small.xml
- Perform Media Gallery synchronization
php bin/magento media-gallery-sync
- Clear Magento cache
php bin/magento cache:clean
- Log in Admin Pannel
- Go to Content - Media Gallery
Expected result (*)
Media Gallery is opened no error messages in dev console
Actual result (*)
❌ Uncaught TypeError: Cannot read property 'clientWidth' of undefined
Note
The bug is unstable, usually appeared on my system after Sign Out/Sign In Magento Admin
The error "comes from" 'masanory.js'
Hi @chalov-anton. Thank you for your report. To help us process this issue please make sure that you provided the following information:
- Summary of the issue
- Information on your environment
- Steps to reproduce
- Expected and actual results
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
- Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
:white_check_mark: Confirmed by @sivaschenko
Thank you for verifying the issue. Based on the provided information internal tickets MC-37871
were created
Issue Available: @sivaschenko, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
@magento I'm working on this
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Thank you for your contributions.
I believe we still need to fix it
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
Please leave it open
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
Please keep it open.
@sdzhepa could you re-triage this issue? JS errors usually causing some not obvious issues. It's better to fix them.
The problem still exists in Magento 2.4.3-p1. The problem appears when you enable Page builder, and go any page builder text area , insert media row , and click on select from media Gallery button. See attached image please
still exists in Magento 2.4.4 for me. Any solution?
i faced the same issue and this one occurs mainly in Google Chrome. On Firefox this is working as expected.
How I can fix this issue on Chrome?
Still exists in 2.4.6-p5
Hi @engcom-Delta. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:
-
- Add/Edit
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.
- Add/Edit
-
- Verify that the issue is reproducible on
2.4-develop
branchDetails
- Add the comment@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on2.4-develop
branch, please, add the labelReproduced on 2.4.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
- Verify that the issue is reproducible on
-
- If the issue is not relevant or is not reproducible any more, feel free to close it.
- Join Magento Community Engineering Slack and ask your questions in #github channel.
Hi @chalov-anton ,
Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop and the issue is not reproducible. Kindly refer the screenshots.
Steps to Reproduce
-
Access Admin Panel.
-
Go to Stores - Configuration - Advanced - System- Media Gallery
-
Set Enable Old Media Gallery to No.
-
Save Config and Clear Cache
-
Logout from Admin
-
Generate small profile for your instance php bin/magento setup:performance:generate-fixtures setup/performance-toolkit/profiles/ce/small.xml
-
Perform Media Gallery synchronization php bin/magento media-gallery-sync
-
Clear Magento cache php bin/magento cache:clean
-
Log in Admin Pannel
-
Go to Content - Media Gallery
-
Manage Gallery
Kindly recheck the issue on latest Magento 2.4-develop instance and Please let us know if you are still facing any issue.
Thanks.