Luma theme shipping tool tip icon cut from leftside #20838

abrarpathan19 · 2019-01-31T08:24:35Z

Preconditions (*)

Magento 2.3 and Magento 2.2.X

Steps to reproduce (*)

Go to checkout- shipping page
Find the field shippingAddress telephone tool tip icon

Expected result (*)

http://prntscr.com/meme4u

Actual result (*)

http://prntscr.com/memgdr

magento-engcom-team · 2019-01-31T08:24:37Z

Hi @abrarpathan19. 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 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

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

yes
no

suryakant-krish · 2019-01-31T08:24:55Z

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

magento-engcom-team · 2019-01-31T08:24:57Z

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

magento-engcom-team · 2019-01-31T08:25:02Z

Hi @suryakant-krish. 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).
Details
If 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.

magento-engcom-team · 2019-01-31T08:26:03Z

Hi @nainesh2jcommerce. 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).
Details
If 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.

magento-engcom-team · 2019-01-31T08:26:39Z

@suryakant-krish Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

magento-engcom-team · 2019-01-31T08:28:14Z

Hi @shikhamis11. 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).
Details
If 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.

suryakant-krish · 2019-01-31T08:28:24Z

@magento-engcom-team,

I have reviewed in my local instance but I need to verify in Magento instance please provide me instance.

nainesh2jcommerce · 2019-01-31T08:30:31Z

reproduce on local

magento-engcom-team · 2019-01-31T08:30:43Z

✅ Confirmed by @nainesh2jcommerce
Thank you for verifying the issue! 👍 Your confirmation will help us to acknowledge and process this report.

suryakant-krish · 2019-01-31T08:32:14Z

Look in this image.

shikhamis11 · 2019-01-31T08:39:26Z

@suryakant-krish I am not able find difference between expected and old one.
This seems not an issue

magento-engcom-team · 2019-01-31T09:20:17Z

Hi @engcom-backlog-nazar. 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).
Details
If 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.

suryakant-krish · 2019-01-31T09:29:54Z

@magento-engcom-team,

I have confirmed the first issue and added labels and do testing on a local machine and provided a screenshot for that. but how you confirm issue @nainesh2jcommerce.

Could you please refer all conversion from top to bottom.

ghost · 2019-01-31T09:39:05Z

@suryakant-krish what's wrong here ?

abrarpathan19 · 2019-01-31T10:03:52Z

@engcom-backlog-nazar This is the screenshot when browser zoom size will be 100%, If you do ctnl + zoom in it you can’t reproduce the issue.
Please find the attachment

Also @nainesh2jcommerce and @suryakant-krish has already reproduce this issue. can you please review their screenshots too.

ghost · 2019-01-31T10:41:24Z

@abrarpathan19 but why i see another result ? and please for simple issue describe problem clearly

suryakant-krish · 2019-01-31T10:50:40Z

@engcom-backlog-nazar,

I reproduced in windows system chrome browser latest version with the 1920 resolution.

Give me an instance for that I will re-confirm that issue.

ghost · 2019-01-31T10:58:34Z

@suryakant-krish ok now clear, this issue related to resolution.

magento-engcom-team · 2019-01-31T11:37:36Z

Hi @shikhamis11. 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).
Details
If 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.

magento-engcom-team · 2019-01-31T11:37:55Z

✅ Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98004 were created

Issue Available: @shikhamis11, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

magento-engcom-team · 2019-02-18T19:20:17Z

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

b76711cfc35e2bd07b734726ad244a7054453375

The fix will be available with the upcoming 2.3.2 release.

dmytro-ch · 2019-02-20T06:17:13Z

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

magento-engcom-team · 2019-02-20T06:17:18Z

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

magento-engcom-team · 2019-02-20T06:17:59Z

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

magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 31, 2019

suryakant-krish self-assigned this Jan 31, 2019

abrarpathan19 assigned abrarpathan19 and unassigned suryakant-krish Jan 31, 2019

suryakant-krish added the Area: Design/Frontend label Jan 31, 2019

nainesh2jcommerce self-assigned this Jan 31, 2019

suryakant-krish added 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 labels Jan 31, 2019

nainesh2jcommerce added Component: Checkout and removed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jan 31, 2019

suryakant-krish added the Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release label Jan 31, 2019

shikhamis11 self-assigned this Jan 31, 2019

nainesh2jcommerce added the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Jan 31, 2019

magento-engcom-team removed the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Jan 31, 2019

magento-engcom-team unassigned nainesh2jcommerce Jan 31, 2019

abrarpathan19 mentioned this issue Jan 31, 2019

Checkout shipping tooltip 20838 #20839

Merged

4 tasks

shikhamis11 added the non-issue label Jan 31, 2019

This comment has been minimized.

Sign in to view

suryakant-krish removed the non-issue label Jan 31, 2019

ghost self-assigned this Jan 31, 2019

ghost added Progress: needs update and removed Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Jan 31, 2019

ghost added Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release and removed Progress: needs update labels Jan 31, 2019

ghost removed their assignment Jan 31, 2019

abrarpathan19 unassigned shikhamis11 Jan 31, 2019

shikhamis11 self-assigned this Jan 31, 2019

shikhamis11 added the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Jan 31, 2019

magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jan 31, 2019

magento-engcom-team unassigned shikhamis11 Jan 31, 2019

magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Feb 18, 2019

magento-engcom-team closed this as completed Feb 18, 2019

priti2jcommerce mentioned this issue Feb 19, 2019

[Backport] Checkout shipping tooltip 20838 #21314

Closed

4 tasks

abrarpathan19 mentioned this issue Feb 19, 2019

[Backport] Checkout shipping tooltip 20838 #21324

Closed

4 tasks

dmytro-ch added the Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release label Feb 20, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Luma theme shipping tool tip icon cut from leftside #20838

Luma theme shipping tool tip icon cut from leftside #20838

abrarpathan19 commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019

suryakant-krish commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019 •

edited by suryakant-krish

Loading

magento-engcom-team commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019 •

edited by abrarpathan19

Loading

suryakant-krish commented Jan 31, 2019

nainesh2jcommerce commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019

suryakant-krish commented Jan 31, 2019 •

edited

Loading

shikhamis11 commented Jan 31, 2019

This comment has been minimized.

magento-engcom-team commented Jan 31, 2019 •

edited by abrarpathan19

Loading

suryakant-krish commented Jan 31, 2019 •

edited

Loading

ghost commented Jan 31, 2019

abrarpathan19 commented Jan 31, 2019 •

edited

Loading

ghost commented Jan 31, 2019

suryakant-krish commented Jan 31, 2019 •

edited

Loading

ghost commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019 •

edited by dmytro-ch

Loading

magento-engcom-team commented Jan 31, 2019

magento-engcom-team commented Feb 18, 2019

dmytro-ch commented Feb 20, 2019

magento-engcom-team commented Feb 20, 2019

magento-engcom-team commented Feb 20, 2019

Luma theme shipping tool tip icon cut from leftside #20838

Luma theme shipping tool tip icon cut from leftside #20838

Comments

abrarpathan19 commented Jan 31, 2019

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

Actual result (*)

magento-engcom-team commented Jan 31, 2019

suryakant-krish commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019 • edited by suryakant-krish Loading

magento-engcom-team commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019 • edited by abrarpathan19 Loading

suryakant-krish commented Jan 31, 2019

nainesh2jcommerce commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019

suryakant-krish commented Jan 31, 2019 • edited Loading

shikhamis11 commented Jan 31, 2019

This comment has been minimized.

magento-engcom-team commented Jan 31, 2019 • edited by abrarpathan19 Loading

suryakant-krish commented Jan 31, 2019 • edited Loading

ghost commented Jan 31, 2019

abrarpathan19 commented Jan 31, 2019 • edited Loading

ghost commented Jan 31, 2019

suryakant-krish commented Jan 31, 2019 • edited Loading

ghost commented Jan 31, 2019

magento-engcom-team commented Jan 31, 2019 • edited by dmytro-ch Loading

magento-engcom-team commented Jan 31, 2019

magento-engcom-team commented Feb 18, 2019

dmytro-ch commented Feb 20, 2019

magento-engcom-team commented Feb 20, 2019

magento-engcom-team commented Feb 20, 2019

magento-engcom-team commented Jan 31, 2019 •

edited by suryakant-krish

Loading

magento-engcom-team commented Jan 31, 2019 •

edited by abrarpathan19

Loading

suryakant-krish commented Jan 31, 2019 •

edited

Loading

magento-engcom-team commented Jan 31, 2019 •

edited by abrarpathan19

Loading

suryakant-krish commented Jan 31, 2019 •

edited

Loading

abrarpathan19 commented Jan 31, 2019 •

edited

Loading

suryakant-krish commented Jan 31, 2019 •

edited

Loading

magento-engcom-team commented Jan 31, 2019 •

edited by dmytro-ch

Loading