Skip to content

26133: Fixed - Coupon code text field not display in proper width in … #30405

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

Conversation

solwininfotech
Copy link
Contributor

…Internet Explorer/EDGE browser

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Coupon code text field not display in proper width in Internet Explorer/EDGE browser #26133 Coupon code text field not display in proper width in Internet Explorer/EDGE browser

Manual testing scenarios (*)

  1. Add a product to the cart
  2. Go to Shipping Cart Page

Before Fix

26133_before

After Fix

26133_after

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)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Oct 10, 2020

Hi @solwininfotech. Thank you for your contribution
Here is 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

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

@solwininfotech
Copy link
Contributor Author

@magento give me test instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

Hi @solwininfotech, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

@solwininfotech
Copy link
Contributor Author

@magento give me test instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

Hi @solwininfotech, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

@solwininfotech
Copy link
Contributor Author

@magento run all tests

@vijay-wagento
Copy link

#dmcdindia2020

@sivaschenko sivaschenko added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Oct 10, 2020
@solwininfotech
Copy link
Contributor Author

@magento give me test instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

@solwininfotech
Copy link
Contributor Author

@magento run all tests

@@ -727,6 +727,13 @@
position: static;
}
}
.content {
.fieldset {
.actions-toolbar {
Copy link
Contributor

Choose a reason for hiding this comment

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

.actions-toolbar selector receives width: 1% from Magento_Paypal/web/css/source/module/_review.less. Can you check it more thoroughly?

Please also check if this works with just .block { .actions-toolbar selector path (remove .content and .fieldset selectors). Add empty lines before and after styles.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@ptylek, thank you for your revision changes that have been done and pushed.

@solwininfotech
Copy link
Contributor Author

@magento run all tests

@solwininfotech solwininfotech requested a review from ptylek October 14, 2020 05:19
@ptylek ptylek added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Oct 14, 2020
@magento-engcom-team
Copy link
Contributor

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

@engcom-Bravo engcom-Bravo self-assigned this Oct 14, 2020
@solwininfotech
Copy link
Contributor Author

@ptylek thank you for your guidance and approving changes.

@engcom-Bravo
Copy link
Contributor

engcom-Bravo commented Oct 15, 2020

✔️ QA Passed

Manual testing scenario

  1. Open Storefront from Internet Explorer browser
  2. Add any product to Cart
  3. Click on Cart, select View and Edit cart
  4. Click on Apply Discount Code
  5. Observe the Enter discount code field size

BEFORE applying changes provided in this PR
Before fix

AFTER switching to the PR
After fix

Note

Also rechecked on Google Chrome browser, the field is not broken
Also rechecked on Luma Theme

@m2-assistant
Copy link

m2-assistant bot commented Oct 16, 2020

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

@solwininfotech
Copy link
Contributor Author

Thank you @ptylek and all to help me to complete this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Design/Frontend Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Event: dmcdindia2020 Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Coupon code text field not display in proper width in Internet Explorer/EDGE browser
7 participants