Alignment Issue when create a new email template admin.

[suryakant-krish]

Preconditions (*)

1. Magento 2.3

Steps to reproduce (*)

1. Login into admin panel > Marketing > Email Templates > Create new Email template Load any default template. Current used For Alignment issue.

Expected result (*)

1. https://prnt.sc/lqykjw

Actual result (*)

1. https://prnt.sc/lqyjq4

[magento-engcom-team]

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

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

• yes
• no

[ghost]

Hi @suryakant-krish did you load some long breadcrumbs ?

[suryakant-krish]

Yes, I have load some long breadcrumbs.

[ghost]

@suryakant-krish SO why you think this is a bug ?

[magento-engcom-team]

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.

[ghost]

@suryakant-krish, I don't think that this is the good idea

[suryakant-krish]

Yes, you are absolutely right but when breadcrumb in single line alignment not proper.
I will work on that with other solution.

[ghost]

@suryakant-krish margin-top: 6px;

[suryakant-krish]

Yes, I have already applied it and added one more commit please review it.

[magento-engcom-team]

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96964, MAGETWO-96965 were created

[magento-engcom-team]

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

• 914382081598500a232f020f4338860ad762c182
• b1c929db5763a5002820c0d2f0ce21dbda50fe87
• 81bae5c088f986a6fe373c9e8e302a4ce4664a4e
• 72438dec51fd3472590675eb24160adf727951fd
• da8b3165e3349c918e62cc1dff90722930fc63b5

The fix will be available with the upcoming 2.3.1 release.