Fix overlap display issue in cms page privacy theme luma

[mrtuvn]

Description (*)

Small change in less styles to avoid overlap visual in cms page privacy-policy theme luma
from mobile screen resolution (<768px)

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes CMS menu issue - Luma Theme #32926

Manual testing scenarios (*)

1. ...
2. ...

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]

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

[mrtuvn]

@magento run all tests

[magento-automated-testing]

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.

[mrtuvn]

@magento run Functional Tests CE

[magento-automated-testing]

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.

[Den4ik]

✅ Looks as useful solution

[magento-engcom-team]

Hi @Den4ik, thank you for the review.
ENGCOM-9090 has been created to process this Pull Request

[dmitriyprime]

✔️ QA passed

[engcom-Alfa]

Hello @mrtuvn, @ptylek and @Den4ik
Thank you for your contribution and collaboration!

I am a new QA engineer and would like to test this Pull Request to unblock and speed up the delivery.
Unfortunately, with the current description, I do not see how it can be tested.
Could you please provide more details on how it can be tested?
For example

• Steps to reproduce and actual/expected result. That I can use to check previous and current behavior to confirm it is fixed.
• Any functional user flows that can be affected by such changes
• Any other advice/ recommendations that will allow us to test it

Before PR fix in Chrome, Firefox, Microsoft Edge and Opera browsers (screenshots are below).

[Den4ik]

@engcom-Alfa You may reproduce and test it with installed sample data from https://github.com/magento/magento2-sample-data

[engcom-Alfa]

✔️ QA Passed

Preconditions:

1. Have a theme luma setup
2. Sample data should be upgraded

Manual testing scenario:

1. Home page, click on "Privacy and Cookie Policy" from footer. Validate by resizing the browser to mobile/ tab sizes.

2. Category page, click on "Privacy and Cookie Policy" from footer. Validate by resizing the browser to mobile/ tab sizes.

3. Product details page, click on "Privacy and Cookie Policy" from footer. Validate by resizing the browser to mobile/ tab sizes.

Before: ✖️ Privacy Policy page header overlapping to Privacy Menu

After: ✔️ Privacy Menu and page header are aligned properly

Tested the same UI alignment navigating from different UI pages like; Home page, product page, category page, cart page etc!
Tested using different browsers like Chrome, Firefox, Microsoft edge

[m2-assistant]

Hi @mrtuvn, 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.