We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Only on a few test cases, a reload of some element will cause a second alert to be queued,
Maybe implement some logic to prevent a re-alert if one already is queued etc.
Not a big issue just some minor optimisation.
The text was updated successfully, but these errors were encountered:
Haven't forgotten about this, just will get to it when the time suits as it's non essential
Sorry, something went wrong.
JamesMatchett
No branches or pull requests
Only on a few test cases, a reload of some element will cause a second alert to be queued,
Maybe implement some logic to prevent a re-alert if one already is queued etc.
Not a big issue just some minor optimisation.
The text was updated successfully, but these errors were encountered: