Hey,

I'm currently having trouble with the CLIENTWINDOW strategy when using frames. In my current case the problem is due to the usage of the Primefaces Dialog-Framework which makes use of iframes for the dialogs. The frame has a special contentWindow which is inspected by the DS code for a window id but it can't find it, because it's on the parent window.

Using window scoped beans is impossible in the iframe as it gets a new window id which makes previous state inaccessible.

Would you consider this a bug or is this intended? Can I somehow append a dsrid or dswid to the URL to get the same window id in the iframe? Using the top window for the window id storage by default would make it impossible to change that aspect selectively and requires changes in the JS file which will probably take some time to bake, so I would prefer the append approach if possible. I can't think of a case where one would want to treat an iframe like a different window but to stay flexible I understand if you want to stick to the current logic, still, do you have a use case like that?

Regards,

Christian

Reply via email to