You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a little hard to explain, so if you need clarification, let me know.
The element <app-snotify> is preventing clicks on other DOM elements, even when there is no notification on the screen. Screenshot
In reference to the screenshot, as long as the element is on the page, I cannot click on the Max items on screen textbox, even after clicking on Clear all. Adding style 'display: none' (or 'visibility: hidden') to the app-snotify element makes it not show up at all and allows the user to click 'behind' it, but also stops any notifications from appearing.
Steps to reproduce:
Open the demo site
Change the position to LEFT-BOTTOM
Click any notification button to create a notification
Wait for the notif to time out
Try to click on a control that was previously covered by the notif.
The text was updated successfully, but these errors were encountered:
<screenshader> is from a Chrome extension; I disabled it and tested the issue and it still happens.
I created a plunker replicating the issue; the user won't be able to click the button at all due to the <app-snotify> element 'blocking' the click event.
This is a little hard to explain, so if you need clarification, let me know.
The element <app-snotify> is preventing clicks on other DOM elements, even when there is no notification on the screen. Screenshot
In reference to the screenshot, as long as the element is on the page, I cannot click on the Max items on screen textbox, even after clicking on Clear all. Adding style 'display: none' (or 'visibility: hidden') to the app-snotify element makes it not show up at all and allows the user to click 'behind' it, but also stops any notifications from appearing.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: