Admin product grid Massaction design issue with sub menu

[ananth-iyer]

Mass action design issue on Product grid, Sales grid, where ever mass action is used.

Preconditions (*)

1. Magento 2.2.x & Magento 2.3.x
2. Chrome
3. Ubuntu

Steps to reproduce (*)

1. Go to Catalog > Products page
2. In Mass Actions drop down > click on Change Status: then you can not see the selected Change Status item & can not close the child drop down to check other items.

Expected result design (*)

1. 

Actual result design (*)

1. 

[magento-engcom-team]

Hi @ananth-iyer. 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.

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

• yes
• no

[ananth-iyer]

I am working on it. #mm19in

[magento-engcom-team]

Hi @sdzhepa. 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]

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

Issue Available: @sdzhepa, 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]

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

• facfa44aa6f5163a1d78f501c94a8a4303b6b631
• 314d3a8ef24d49f5a55cf6ca3efe5bdfef025b4d
• 631c6b1a2c13c34bf2689148b1ec7ee6d88d2391
• 524eef39230cd60d2a4f32f6827c6f238d574957

The fix will be available with the upcoming 2.3.2 release.