I am afraid these are not known problems and at this point I can only offer assumptions based on previous experience and common issues.
@Adi: Can you confirm the ID of the RadWindow that is being opened is a valid string without special characters in it, e.g. "arg\one" could be invalid and special symbols should be escaped for passing them to a querystring/URL.
Also, calling radopen() is equivalent to calling show() and center() so these are not needed. Even so, a call to center() should be after a call to show() because you could not center a popup that is not shown.
What I also see is that the argument you pass to the function is called "id" but the variable used in the function body is "artid" which is likely to cause a JS error by itself, and thus break the RadWindows.
@Edward: I do not see a reason for this problem in the provided code and we are not aware of issues between IE10 and the latest official release. Can you confirm you are using Q2 2013 SP1?
Another thing that you can try is examining the problematic browser, as the issue may lie with it:
- does resetting its settings help?
- are there broken requests (e.g. for scripts) - this can be caused by AV, firewalls or proxies
- does disabling its addons/plugins help? One/several of them may be interfering with the page and breaking RadWindow. We had a similar report for HootSuite recently.
- it is also possible that IE10 is overall broken in terms of MS AJAX. This sticky thread
will offer more information on the matter.
If you can share live URLs where we can examine the pages it may help us find useful information.
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed