This behavior is not coming from the RadWindow or the way it loads its content, but from the way the content in your PageView is loaded. You seem to be using its ContentUrl so it has its own context (window and document objects) because it gets loaded in an iframe. The RadWindow, being HTML defined in the iframe, cannot violate its boundaries (this is a browser feature - limiting the content of iframes inside the frames).
The following help articles treat similar cases:
What you can do is to open the RadWindow from the parent page, e..g:
where radopen(url, wndName); assumes the place of the current opening logic. You can see various ways to open a RadWindow here: http://www.telerik.com/help/aspnet-ajax/window-programming-opening.html. You can put the opening logic in a dedicated function and call that instead
Note that this requires the following:
- the presence of a RadWindowManager or the desired RadWindow on the main page
- if the RadWindow has handlers, they must be in the cotnext of the main page, because this is where it is defined.
I hope this explains the situation.
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.