Hover colour not applied on static grids in admin

[fredden]

Preconditions

1. Have more than one admin user
2. Tested on 2.4.3-p2 and ef0ffcd37470e83337133a167dc4504f86037f28 (ie, current HEAD of 2.4-develop branch)

Steps to reproduce

1. Navigate to a static grid - for example the admin user grid (System -> Permissions -> All Users)
2. Notice background colours shown on each row.
3. Hover over the first row.
4. Notice background colour of hovered-over row.
5. Hover over the second row.
6. Notice background colour of hovered-over row.

Compare this to a dynamic grid where the hover background colour works as expected. (For example, the Design Configuration grid behaves as expected - Content -> Design -> Configuration.)

Expected result

1. All rows highlight as they are hovered over.

Screen-shots of Admin Users grid working as expected (CSS manipulated on-page)

 

---

Screen-shots of Design Configuration grid working as expected

 

---

Actual result

1. Only odd-numbered rows highlight as they are hovered over.
2. Even-numbered rows do not show any differently when hovered over or not.

Screen-shots of Admin Users grid as it currently behaves

 

---

Technical details

It may help a developer to know that the hover style is here: https://github.com/magento/magento2/blob/610f7f51faa94639da29f8001aded7559f114c54/app/design/adminhtml/Magento/backend/Magento_Ui/web/css/source/module/_data-grid.less#L190-L194

And the alternating-row style is here: https://github.com/magento/magento2/blob/610f7f51faa94639da29f8001aded7559f114c54/app/design/adminhtml/Magento/backend/Magento_Ui/web/css/source/module/data-grid/_data-grid-static.less#L18-L28

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [x] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @fredden. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

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

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @engcom-November. 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: :point_down:

• [ ] 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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-November]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-November, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-November]

Verified the issue on Magento 2.4-develop branch and the issue is reproducible. Hovering on odd numbered rows - background color is changing as expected. Hovering on even numbered rows - Background color is not changed. Issue: Expected behavior: Behavior should be consistent across all pages (Ex: Content - Design - Configuration) - Hovering all rows - Background color is changing as expected.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-2916 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.magento.com/browse/AC-2916

[Usik2203]

@magento I am working on this