Is anyone else having this issue? Works fine with Chrome, Edge and Firefox.
Thanks,
Chris Cartrett
Is anyone else having this issue? Works fine with Chrome, Edge and Firefox.
Thanks,
Chris Cartrett
I've never had any issues with the lookup events not firing. Are you sure it is the event that's not working, or maybe the code inside of the event isn't compatible with IE?
Try using the following code, which works for me in every browser, to test it out:
$(document).on('onloadlookupfinished',function(){ alert('finished'); });
I am using the following code and I only get an alert a few times after refreshing. Then it no longer appears. Seems to be intermittent...
$(document).ready(function(){ $(document).on("onloadlookupfinished", function () { alert('finished'); }); //on load lookup finish }); //after document ready function
Try taking the code out of the ready event to see if you get a different result. You don't need to wait for the ready event to fire before assigning the onloadlookupfinished handler.
Is that the only JavaScript you have added to the form?
Oh no, I have a ton of javaScript on there. I added some code to see if the onloadlookupfinished handler runs. If it doesn't, I retrigger the code that it runs. Working with Internet Explorer. I'll try taking it outside of the ready event and see what happens. Thanks for the idea :)
There's also a possibility that something else in your code is the "source" of the issues. For troubleshooting purposes, I would disable the rest of the JavaScript and test it a piece at a time to try and pinpoint the actual problem code.
I tried that. I am leaning toward the idea of it being a gpo that includes permissions for internet explorer.
Could be. Are you getting any errors in the console? The IE dev tools/console isn't the most helpful, but it is worth a look. Another common issue for IE is compatibility mode.
I can't even get to the console. I have to run it as an admin to get to the console. That is due to a gpo restricting IE.
So it is pretty locked down. Have you tested to see if you get the issue while running it as an admin? If not, it would probably support your GPO theory.
I'll test it out.