Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix notify_badge.tsx toggle not working #208996

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

Eamonn-OL
Copy link

@Eamonn-OL Eamonn-OL commented Jan 30, 2025

Summary

At the moment, when you click on the notify badge in the "rules" page, then click it again (expecting a toggle) it actually gets stuck on the page and only a refresh can fix it.

This change adds a toggle and implements it in place of the "openPopover" to correctly toggle the state of the popover.

Checklist

  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Release Notes

Fixes an issue where the popover in the rules page may get stuck when being clicked more than once.

Before:

Screen.Recording.2025-01-30.at.17.10.37.mov

After:

Screen.Recording.2025-01-30.at.19.14.00.mov

At the moment, when you click on the notify badge in the "rules" page, then click it again (expecting a toggle) it actually gets stuck on the page and only a refresh can fix it.

This change adds a toggle and implements it in place of the "openPopover" to correctly toggle the state of the popover.
Fixing another case that was missed for indefinitesnooze.
A minor bug with this change is that the bell icon stayed shown until a click was registered elsewhere in the screen.

This adjustment fixes this - keeping the closepopover/togglepopover functional, but also fixing the minor problem with the bell icon remaining stuck/not respecting hoverover.
@Eamonn-OL Eamonn-OL marked this pull request as ready for review January 30, 2025 19:16
@Eamonn-OL Eamonn-OL requested a review from a team as a code owner January 30, 2025 19:16
@elasticmachine
Copy link
Contributor

elasticmachine commented Jan 30, 2025

💔 Build Failed

Failed CI Steps

History

Copy link
Contributor

@adcoelho adcoelho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the small fix 👍

@cnasikas cnasikas added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v9.0.0 Feature:Alerting/RulesManagement Issues related to the Rules Management UX backport:prev-minor Backport to (9.0) the previous minor version (i.e. one version back from main) v9.1.0 labels Feb 1, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@cnasikas cnasikas added the bug Fixes for quality problems that affect the customer experience label Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:prev-minor Backport to (9.0) the previous minor version (i.e. one version back from main) bug Fixes for quality problems that affect the customer experience Feature:Alerting/RulesManagement Issues related to the Rules Management UX release_note:fix Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v9.0.0 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants