Just a comment...
In our application, we open radwindows from the client side in javascript. Some of those dialog are used to "batch edit" many records selected in a page. To pass the selected records to the dialog, we append their IDs in the query string of the radwindow (as described in the "Using the URL Query String to Provide Arguments to RadWindow" chapter in the documentation) The problem is that in IE, the URL is limited to 2000 characters, so if we select too many record, this create an invalid url.
So it would be nice if we could open a radwindow from the client-side using a POST instead of a GET to remove this limitation.
Thanks
In our application, we open radwindows from the client side in javascript. Some of those dialog are used to "batch edit" many records selected in a page. To pass the selected records to the dialog, we append their IDs in the query string of the radwindow (as described in the "Using the URL Query String to Provide Arguments to RadWindow" chapter in the documentation) The problem is that in IE, the URL is limited to 2000 characters, so if we select too many record, this create an invalid url.
So it would be nice if we could open a radwindow from the client-side using a POST instead of a GET to remove this limitation.
Thanks
1 Answer, 1 is accepted
0
Hi Bob,
This is not possible - RadWindow is yet another IFRAME and it acts just like one. To be able to post some data on the server, you first need to load the Url and get the corresponding content page.
In scenario like yours, I would suggest to use argument that you could send to the content page via the Client-Side API. Once you have them on the client in the content page, you need to make a postback / Ajax callback to send them to the server.
Sincerely yours,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
This is not possible - RadWindow is yet another IFRAME and it acts just like one. To be able to post some data on the server, you first need to load the Url and get the corresponding content page.
In scenario like yours, I would suggest to use argument that you could send to the content page via the Client-Side API. Once you have them on the client in the content page, you need to make a postback / Ajax callback to send them to the server.
Sincerely yours,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.