search

PaulNieuwelaar / notifyjs

Other
31 stars 9 forks source link

Notifications can not be closed #4

Closed DonQuiProgger closed 6 years ago

DonQuiProgger commented 6 years ago

I experienced an issue with the Notifications on firefox and chrome (didn't check edge). The Notifications can not be closed whether by the built-in duration parameter nor by the close button. This happens sometimes depending on how fast the page loads and can be mitigated by adding a timeout function before actually calling Notify.add(...). When this error happens i also tried calling manually jQuery to close the specific Notification but this did not work either. Tested this on a dynamics test instance, Version should be 9.2.....

PaulNieuwelaar commented 6 years ago

Hi, I tested this and it seems to be working OK for me. Are you calling it in the form onload event? Are you loading the Notify.js web resource anywhere else, i.e. from a ribbon button or other web resource loaded into the page? Any other info about how you're using it or how to reproduce the issue would be appreciated. Cheers, Paul

DonQuiProgger commented 6 years ago

Hi, thx for the fast answer. Yes, you are right, i use a javascript with a form onload event which calls the Notify.add() function. The notifiy.js library is added to the form libraries before my javascript. Maybe i am doing something wrong here.? There is no other loading of the Notify.js web resource anywhere else.

I believe that this error has something to do with jquery because i can still address and hide the elements when using queryselector. This error is also independent of the form, because i tried it in accounts and contacts.

DonQuiProgger commented 6 years ago

I just created a new dynamic instance and was not able to reproduce the error. The major difference between the new and old instance is that i enabled all scenarios (sales, project service...) during setup of the old instance.

PaulNieuwelaar commented 6 years ago

Hi, do you have a different version of jquery being loaded onto the form somewhere?

DonQuiProgger commented 6 years ago

Well... i don't have the test instance anymore (trial ended) but in case the error appears again, how do i check this?

PaulNieuwelaar commented 6 years ago

Hi, you can check it from the form properties, and check the js libraries being loaded into the form. One of those add-ons might have been loading an old jQuery version onto the form which doesn't have some of the features required.