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
Currently, ngn class defines a style of display: block. If there is another container on the page with a fixed position (a "full-screen" div, for example) the ng-notify div can interfere with the ability to focus on elements in the other div. Once a notification is displayed/hidden (and the style is set to none) it is no longer an issue.
For my case I was able to fix it by overriding the display style:
div.ngn {
display: none;
}
For my use case this works fine, though I'm not sure what impacts it might have with other ng-notify configuration options.
The text was updated successfully, but these errors were encountered:
@antch thanks for the feedback. I believe the intent was to have display: none in there but for testing or whatever other reason, block had gotten set. I ran through tests in each browser and found no issue with replacing it with display: none and it makes more sense to me to have the div hidden until it's triggered, so I've gone ahead and made that change in the repo. Thanks for the feedback, much appreciated!
Currently,
ngn
class defines a style ofdisplay: block
. If there is another container on the page with a fixed position (a "full-screen"div
, for example) the ng-notifydiv
can interfere with the ability to focus on elements in the otherdiv
. Once a notification is displayed/hidden (and thestyle
is set tonone
) it is no longer an issue.For my case I was able to fix it by overriding the
display
style:For my use case this works fine, though I'm not sure what impacts it might have with other ng-notify configuration options.
The text was updated successfully, but these errors were encountered: