Load resizable jquery-ui chunk for knockout resizable binding only when actually used

[martasiewierska]

Description (*)

Resizable knockout binding is hardly never used on the frontend, it also does not work there (see #32753) As we are constantly often struggling to reduce unused javascript and improve performance metrics for our shops I would like to add this small step to remove not used javascript.

Manual testing scenarios (*)

1. Create empty page without any other component that require jquery/ui-modules/resizable.js
2. Check if jquery/ui-modules/resizable.js file is not loaded in Network tab (no js bundling)
3. Create test UIComponent with resizable knockout binding
4. Check if jquery/ui-modules/resizable.js file is loaded in Network tab (no js bundling)

Questions or comments

Fixed Issues (if relevant)

1. Fixes Resizable knockout binding does not work on the frontend #32753

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @martasiewierska. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests 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.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ptylek]

Looks good to me. Let's wait for test results.
@magento run all tests

[mrtuvn]

@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE

[ihor-sviziev]

@mrtuvn, I believe it would be too hard to cover these changes with any test. I prefer not to cover it. What do you think?

[ihor-sviziev]

@magento run all tests

[ihor-sviziev]

@magento run Functional Tests B2B, Functional Tests EE, Integration Tests, WebAPI Tests

[ptylek]

@magento run Functional Tests B2B, Functional Tests EE, WebAPI Tests

[ihor-sviziev]

@magento run Functional Tests B2B, Functional Tests EE

[dmitriyprime]

✔️ QA passed

[ihor-sviziev]

Moving this PR back to "accept" status... It looks like it was moved due to some mistake

[m2-assistant]

Hi @martasiewierska, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.