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

make sure a toast has not already been dismissed when dismissing it #868

Conversation

chandlerprall
Copy link
Contributor

Addresses elastic/kibana#19263 by making EuiGlobalToastList make sure it hasn't already dismissed a toast when it goes to dismiss a toast.

Copy link
Contributor

@cjcenizal cjcenizal left a comment

Choose a reason for hiding this comment

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

🔧LGTM! My only suggestion would be to add a test to guard against a regression. Toast close buttons are decorated with data-test-subj="toastCloseButton", and we can use the findTestSubject test helper to find this element and simulate multiple clicks on it.

@chandlerprall
Copy link
Contributor Author

I couldn't replicate the issue within the existing test setup. I'll merge this to unblock things and then circle back and give it another try. Thanks @cjcenizal !

@chandlerprall chandlerprall merged commit 83696ee into elastic:master May 23, 2018
@chandlerprall chandlerprall deleted the bug/kibana-19263-notification-double-dismiss branch May 23, 2018 16:02
@cjcenizal
Copy link
Contributor

Sounds good!

chandlerprall added a commit to chandlerprall/eui that referenced this pull request May 24, 2018
…lastic#868)

* make sure a toast has not already been dismissed when dismissing it

* changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants