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

Fixes 'unexpected token case' on massaction_extended template #32798

Open
wants to merge 2 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

vrielsa
Copy link

@vrielsa vrielsa commented Apr 20, 2021

Description (*)

When using HTML minification the massaction_extended template (from the Magento_Catalog module) causes a javascript error ('unexpected token case'). Adding proper closing tags to the break statement fixes this.
Also removed deprecated escape calls.

Steps for reproducing the issue

  • Create a custom product grid using the app/code/Magento/Catalog/view/adminhtml/templates/product/grid/massaction_extended.phtml template
  • Enable HTML minification using Cloudflare
  • Visit the page with the custom product grid

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
Copy link

m2-assistant bot commented Apr 20, 2021

Hi @vrielsa. 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

@vrielsa
Copy link
Author

vrielsa commented Apr 20, 2021

@magento give me test instance

@magento-deployment-service
Copy link

Hi @vrielsa. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@vrielsa
Copy link
Author

vrielsa commented Apr 20, 2021

@magento run all tests

@mrtuvn
Copy link
Contributor

mrtuvn commented Apr 20, 2021

@magento run Unit Tests, Functional Tests B2B

@mrtuvn
Copy link
Contributor

mrtuvn commented Apr 22, 2021

cc: @vrielsa can you update PR description steps to reproduce issue for QA can re-check

@mrtuvn mrtuvn added Cleanup Risk: low Priority: P3 May be fixed according to the position in the backlog. labels Apr 24, 2021
@mrtuvn
Copy link
Contributor

mrtuvn commented Apr 24, 2021

@gabrieldagama should we need cover this change by some kind of tests

@mrtuvn
Copy link
Contributor

mrtuvn commented Apr 24, 2021

deprecated escape calls still called in another template
reference link below
https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Backend/view/adminhtml/templates/widget/grid/massaction_extended.phtml

@vrielsa
Copy link
Author

vrielsa commented Apr 24, 2021

@mrtuvn I'll update the description later today. I'll update the widget/grid/massaction_extended.phtml as well if you like

@mrtuvn
Copy link
Contributor

mrtuvn commented Apr 28, 2021

Yes you are feel free to do that or maybe do it later via another seperate PR

@mrtuvn mrtuvn added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Cleanup Component: Catalog Partner: PHPro partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: review Release Line: 2.4 Risk: low
Projects
Status: Review in Progress
Development

Successfully merging this pull request may close these issues.

3 participants