A minimal sample is to just use a jqxDrowdownList with items with jQuery 3.6.0.
You wont get any exception because this is caught inside jqWidgets and then it falls back to “e(t).html(i)”.
But it is a serious performance and stability problem when you have many items and many dropdowns.
Simply put jqWidgets should never call a function that it assumes exists.
The assumption here is that you have “.access()” when you have “.on()”.
This is no longer true for quite some time in jQuery.
The apropriate thing to do would be to check if “.access” exists and is a function before calling it.
You can also enable “Pause on caught exceptions” in the chrome/edge dev tools and you will see that you jump to this place where it calls “access” which does not exists.
Since .html() is called for each item to draw it you will get thousands of these when you have a complex ui with a lot of items in dropodowns.
But this same asumptions is being done in many places in jqWidgets, not only in jqxDropdown, basically everywhere it wants to render the html for something. Even in jq.core.
