I came up with another possible solution for this problem and I believe this should match the desired outcome - open RadEditor's dialogs in a window that resides on the same page as the RadWindow control that contains the editor. I have attached a sample project implementing this approach.
Now regarding your questions:
Yes, "classic" dialogs will be detected as pop-ups and will be blocked because they are standard browser windows.
And again, yes that is exactly how it works:
- RadWindow is an IFRAME which content is a completely different document.
- If you have RadEditor inside RadWindow, RadEditor's dialogs are elements of RadWindow's document.
As for a similar to RadWindow control, we have RadDock
which are used for different purpose and I do not think that they are suitable for your scenario.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.