Hello @Z!
Thanks for reporting the issue, we do want to get to the bottom of it, but I'm not sure your test case works the way you wanted us to see it reproducing the issue.
I can load the test case and click 'TESTSET'. It loads the ajax page inside the last tab in the tab panel with the 2 seconds delay.
But then I choose a value from the dropdown right below the button and I get a 'cannot read property of undefined' error from line 97 in your first code block. This may indicate that you have some setting on your project (Web.config maybe?) that's overriding defaults, such as the example runs on your side without problems whereas it breaks in our side.
Could you test your sample on a clean project on your side? The solution to the error may be simple but it could just avert us from the point which is reproducing the issue the way you do it in your side.
Well, even trying to figure out the error, I couldn't get the twice up load event that (I presume) should have hit the 'debugger;' line (your code line 28) twice when I clicked 'load...' from the select window (once I could make it show up).
I am not sure, I see several things on your test case that makes it maybe more complex than it should. Here's some points of question:
- There are several references to
/ta/Support/ajax
. Are them all required to reproduce the issue? Are they supposed to point to the 'ajax.aspx' file you named in your code?
- Is the
.aspx extension missing from the ajax link by purpose, maybe you are using the
FriendlyURLs feature in your project?
- I see a commented block right in the line that triggers the error (97 in your first code block), is that there for a reason?
- Are all the 5 tabs in the
TabPanel1 required to reproduce the issue? The third has a reference to the
/ta/Support/ajax
url as well but I don't see your instructions on reproducing the issue mentioning it at any point
- Is the custom user control (controls.ascx) required to reproduce the issue? I mean, if you copy-paste the user control inside the main page, you then no longer is able to reproduce the issue?
All this looks pretty distracting while trying to both reproduce the issue and being able to focus on the real problem. If those things are not required to reproduce the issue, it would be much easier to pinpoint the reason and avoid this thread from taking several pages until the issue can be tackled with.
That said, can you review the points above (check if you can reproduce the issue with the user control copypasted inside the main page, for example) and let us know, maybe then providing a test case reduced to the bare minimum amount of code required to reproduce the issue so we can focus on the actual issue?
Please also give a try of your test case in a clean project. Just create a new solution, with a WebForms project. Don't use a WebForms template (use the Empty template), just check the 'WebForms' references binding while creating the new project and then installing the Ext.NET NuGet package on it.
Attachment 24923
Besides, I've run your test case using google chrome. Ran the test case without VisualStudio debugging and enabled chrome's developer tools/debugger before loading the page (so that it breaks in the 'debugger;' line).
Looking forward to your feedback! :)