This is, indeed, a really strange report. I have not seen such issues with the control and at this point I can advise the following:
- try the latest version of the controls to see if this helps
- make sure you pass integers to the moveTo(x, y) method of the popup. The parseInt() function can help for this
- add a check before moving it: if(wndReference.get_popupElement()) wndReference.moveTo(x, y); because it is possible that the method is called too early, before the popup element is created (this happens with JS, when the RadWindow is first shown). If it were a timing issue a timeout would usually resolve it, so you can try higher values like 100 or 200 ms.
- make sure the button does not perform a postback after executing the JS function that opens the next popup, especially if the ContentTemplate of the RadWindow is used.
If neither of these ideas help - sharing some code that can be used to reproduce the problem, along with the version number that you are using will help us investigate this case.
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