Index Management Grid: Align issue with checkboxes

[yurylapi]

Preconditions

1. Install or update Magento 2.3 to the last version;

Steps to reproduce

1. Login to admin panel;
2. Go to the System->Tools->Index Mangement;
3. You will see a broken grid;
   

Expected result
The grid table aligns checkboxes properly.

Actual result

1. Current styles breaks checkbox alignment in Index Management Grid table;

Additional details

1. Apparently this line was coming after merge-conflict resolving, but should not be there.
   

   magento2/app/design/adminhtml/Magento/backend/Magento_Ui/web/css/source/module/_data-grid.less

   Line 394 in 7aa9456

   vertical-align: top;

2. This line breaks the table alignment, but apparently it's already resolved in 2.3-development branch.
   

   magento2/app/design/adminhtml/Magento/backend/Magento_Ui/web/css/source/module/_data-grid.less

   Line 1078 in 7aa9456

   display: unset;

[m2-assistant]

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

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

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

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @engcom-Charlie. 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 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. Add label Issue: Confirmed once verification is complete.

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

[engcom-Charlie]

Hello @yurylapi
As you know this issue is resolved now. I think it was reported earlier. That fix will be included in Magento 2.3.4 .
So no sense to confirm your issue. We can just close it.

Thanks for your report!

[yurylapi]

Perfect, thanks

…

On Wed, Nov 27, 2019 at 1:57 PM Maxim Vdovenko ***@***.***> wrote: Closed #25773 <#25773>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#25773?email_source=notifications&email_token=AKVDQRCJ576GHYIZQVFZN4LQVZVE5A5CNFSM4JSGK2R2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVEBQBPA#event-2835546300>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKVDQRA5FZTTE5ISC3Z35TDQVZVE5ANCNFSM4JSGK2RQ> .