We are currently looking for possibilities to address the problem in the easiest possible way for the developers.
There are several options and each has some pros and cons.
We are currently leaning towards the following implementation:
: Editor is in a RadWindow or in simple iframe [i.e, in a different document that only occupies part of the page. We want, when an editor dialog open, that it renders in the context of the top browser window so that its modality covers the whole page, as well as it is possible to move and resize the window on the whole page.
Possible solution we are currently experimenting with
1. Add a ScriptManager and a RadWindowManager Prometheus on the top browser page [must be done by the developer]
2. When the editor opens a dialog, it will check whether the current window is the top browser window. If it is not, it will try to access the top browser window (possible if the two pages are from the same domain), and get a reference to a RadWindowManager
. If it gets a reference to the manager, it will use it to create the windows in the context of this window manager [the RadEditorPrometheus code will need to be changed to do this].
There is one important question to be addressed with this approach - it is possible that the developer aready uses a RadWindowManager on the top page, and perhaps has written client code that make break if the editor [or editors] start using the same RadWindowManager
One option would be to hardcode the editor to use the RadWindowManager only if it has a special ID, e.g. "RadEditorDialogProvider
I am writing all this hoping to hear your suggestions and comments on the approach, so that we decide on an approach and implement it.
the Telerik team