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

View and Edit Cart link not aligned in middle because bellow the link a blank div (class="minicart-widgets") existing has 15px margin top, this div (class="minicart-widgets" ) should be display none or should not come if has no content, should only display if has content #20382

Closed
irajneeshgupta opened this issue Jan 17, 2019 · 12 comments
Assignees
Labels
Component: Checkout Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@irajneeshgupta
Copy link
Member

View and Edit Cart link not aligned in middle because bellow the link a blank div (class="minicart-widgets") existing has 15px margin top, this div (class="minicart-widgets" ) should be display none or should not come if has no content, should only display if has content.

Preconditions (*)

  1. Magento 2.3
  2. php 7.2

Steps to reproduce (*)

  1. Open frontend
  2. Add any product in cart and go to minicart and see View and Edit Cart Link (you will get issue )
  3. you will see extra space bellow the link and now inspect you see bank div has 15px margin top.

Expected result (*)

mini_sol

Actual result (*)

mini_issue

@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Jan 17, 2019

Hi @irajneeshgupta. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@irajneeshgupta do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 17, 2019
@cedarvinda cedarvinda self-assigned this Jan 17, 2019
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Jan 17, 2019

Hi @cedarvinda. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@cedarvinda
Copy link
Member

@magento-engcom-team give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @cedarvinda. Thank you for your request. I'm working on Magento 2.3-develop instance for you

@cedarvinda cedarvinda added the Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed label Jan 17, 2019
@magento-engcom-team
Copy link
Contributor

Hi @cedarvinda, here is your Magento instance.
Admin access: https://i-20382-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@cedarvinda cedarvinda added Component: Checkout Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jan 17, 2019
@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jan 17, 2019
@magento-engcom-team
Copy link
Contributor

@cedarvinda Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97700 were created

@cedarvinda
Copy link
Member

@magento-engcom-team give me 2.2-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @cedarvinda. Thank you for your request. I'm working on Magento 2.2-develop instance for you

@magento-engcom-team
Copy link
Contributor

Hi @cedarvinda, here is your Magento instance.
Admin access: https://i-20382-2-2-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@cedarvinda cedarvinda added the Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release label Jan 17, 2019
@irajneeshgupta irajneeshgupta added the Progress: PR Created Indicates that Pull Request has been created to fix issue label Jan 18, 2019
irajneeshgupta pushed a commit to irajneeshgupta/magento2 that referenced this issue Jan 21, 2019
@magento-engcom-team
Copy link
Contributor

Hi @irajneeshgupta. Thank you for your report.
The issue has been fixed in #20383 by @irajneeshgupta in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.1 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Feb 10, 2019
magento-engcom-team added a commit that referenced this issue Feb 10, 2019
 - Merge Pull Request #20383 from irajneeshgupta/magento2:Magento-2.3-develop-PR
 - Merged commits:
   1. 5aa0cd0
amol2jcommerce pushed a commit to amol2jcommerce/magento2 that referenced this issue Feb 11, 2019
irajneeshgupta pushed a commit to irajneeshgupta/magento2 that referenced this issue Feb 11, 2019
@magento-engcom-team magento-engcom-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Feb 12, 2019
@magento-engcom-team
Copy link
Contributor

Hi @irajneeshgupta. Thank you for your report.
The issue has been fixed in #21124 by @irajneeshgupta in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.9 release.

magento-engcom-team added a commit that referenced this issue Feb 12, 2019
 - Merge Pull Request #21124 from irajneeshgupta/magento2:2.2-develop-PR-port-20383
 - Merged commits:
   1. 05848e5
@kozie
Copy link

kozie commented Jun 28, 2019

@irajneeshgupta Why did you add an if statement to the following line?

<div id="minicart-widgets" class="minicart-widgets" if="getRegion('promotion').length">

It doens't make sense seeing the current issue and it's causing my widgets to not show up anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Checkout Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

4 participants