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

Element app-snotify remains in DOM and prevents clicks #11

Closed
jtwotimes opened this issue Jun 1, 2017 · 3 comments
Closed

Element app-snotify remains in DOM and prevents clicks #11

jtwotimes opened this issue Jun 1, 2017 · 3 comments
Assignees
Labels

Comments

@jtwotimes
Copy link
Contributor

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:

  1. Open the demo site
  2. Change the position to LEFT-BOTTOM
  3. Click any notification button to create a notification
  4. Wait for the notif to time out
  5. Try to click on a control that was previously covered by the notif.
@artemsky
Copy link
Owner

artemsky commented Jun 1, 2017

I understood you.
Cannot reproduce it.

Can you please share more details about your workflow.

And one question. What is this <screenshader></screenshader> element. And from where it comes from. I don't have it in my demo app.

@jtwotimes
Copy link
Contributor Author

<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.

@artemsky
Copy link
Owner

artemsky commented Jun 1, 2017

Yeah! now i see the problem.
@mtrdp642 Thank you for reporting.

@artemsky artemsky self-assigned this Jun 1, 2017
@artemsky artemsky added the bug label Jun 1, 2017
artemsky added a commit that referenced this issue Jun 5, 2017
@artemsky artemsky closed this as completed Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants