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

34084: Replaced tag 'br' to a valid version #34136

Conversation

AZiniukhin
Copy link
Contributor

Description (*)

Deprecated "<br>" and "</br>" tags were changed to their valid version "<br />"

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Replace </br> with a valid version of <br /> #34084

Manual testing scenarios (*)

Questions or comments

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 Sep 21, 2021

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

@ihor-sviziev
Copy link
Contributor

@xmav, I guess this change is related to the jquery update. Could you check it?

@BarnyShergold
Copy link

@magento run all tests

@magento-automated-testing
Copy link

Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds.

@xmav
Copy link
Contributor

xmav commented Sep 21, 2021

Hi @ihor-sviziev
yes, jQuery require tags to be properly closed. It is important to have "correct" tags in html that will be manipulated by jquery. From that point it is not needed to update tags in translations like Warning!<br />This action will remove this user from already assigned role.<br />Are you sure? as this should not affect jquery but will be backward incompatible

@BarnyShergold
Copy link

@magento run all tests

@magento-automated-testing
Copy link

Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds.

@BarnyShergold
Copy link

@xmav - Can you fix the conflicting file please and check tests will run - they won't at the moment as you can see.

@xmav
Copy link
Contributor

xmav commented Sep 21, 2021

@BarnyShergold I believe this should be addressed by @AZiniukhin

@hostep
Copy link
Contributor

hostep commented Sep 21, 2021

Maybe take the following comment into account as well? Or are there valid cases for keeping a space in the tag in the year 2021?

Copy link
Contributor

@orlangur orlangur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use a shorter tag version as suggested in #34136 (comment)

After changes are applied and all builds are green, please squash them into a single commit so that we have perfectly clean history 😉

@DanielRuf
Copy link
Contributor

Magento 2 uses html5 as doctype so this makes no real difference afaik.

Where is documented, that <br> does not work for jQuery? Because this is the valid version for empty elements in html5, <br/> would be xhtml.

@DanielRuf
Copy link
Contributor

DanielRuf commented Sep 23, 2021

@BarnyShergold
Copy link

@BarnyShergold I believe this should be addressed by @AZiniukhin

Yes - sorry, wrong tag entered!

@orlangur
Copy link
Contributor

@DanielRuf ok :) We have too many <br /> with or without space currently in code but without enforcing only one variant let's not touch them.

Copy link
Contributor

@orlangur orlangur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AZiniukhin as pointed out in discussion <br> is perfectly valid so don't touch them.

Just change all </br> to <br>.

After changes are applied and all builds are green, please squash them into a single commit so that we have perfectly clean history 😉

@Den4ik
Copy link
Contributor

Den4ik commented Sep 24, 2021

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@BarnyShergold
Copy link

@magento run functional tests CE,Integration Tests,Static Tests,Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@BarnyShergold
Copy link

@magento run functional tests CE,Integration Tests,Static Tests,Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@orlangur
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@AZiniukhin
Copy link
Contributor Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Dash
Copy link
Contributor

engcom-Dash commented Oct 23, 2024

Hello @AZiniukhin ,

Thank you for your contributions!

Please resolve the conflict so we can proceed with this PR.

Thanks again!

@engcom-Dash
Copy link
Contributor

Closing this PR since it has not been updated in a while. Please feel free to reopen if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Component: multiple Priority: P3 May be fixed according to the position in the backlog. Release Line: 2.4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Replace </br> with a valid version of <br />
10 participants