Wicket Modal Window - IFrame
I'm currently running into an issue with the wicket modal window. My situation is this. Wicket App A contains an IFrame sourcing Wicket App B. B has an Wicket IFrame modal window on one of it's pages. When Wicket.Window.create in modal.js is called from B, the Wicket.Window is pulled from window.parent.Wicket.Window which has been created in A. Now the remaining functions called on Wicket.Window are referencing functions from A modal.js This becomes a problem when the createDOM in modal.js is called. The div tag containing the modal html from B is created in A's document. The iframes src is relative so the content for the modal is not found. One solution is to have Wicket App B use WebRequestCodingStrategy and encode all it's url's from relative to absolute. This is not an optimal solution as I have no control over the multiple wicket apps that will be sourced in Wicket App A's iframe. Is there anyway to essentially namespace the Wicket.Window so B does not pick up A's objects? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Modal Window - IFrame
On Wed, Sep 3, 2008 at 10:13 PM, Shaun Thompson [EMAIL PROTECTED] wrote: I'm currently running into an issue with the wicket modal window. My situation is this. Wicket App A contains an IFrame sourcing Wicket App B. B has an Wicket IFrame modal window on one of it's pages. When Wicket.Window.create in modal.js is called from B, the Wicket.Window is pulled from window.parent.Wicket.Window which has been created in A. Now the remaining functions called on Wicket.Window are referencing functions from A modal.js This becomes a problem when the createDOM in modal.js is called. The div tag containing the modal html from B is created in A's document. The iframes src is relative so the content for the modal is not found. One solution is to have Wicket App B use WebRequestCodingStrategy and encode all it's url's from relative to absolute. This is not an optimal solution as I have no control over the multiple wicket apps that will be sourced in Wicket App A's iframe. Is there anyway to essentially namespace the Wicket.Window so B does not pick up A's objects? I don't think so. And the modal window wasn't really meant to be able to contain different/multiple applications. -Matej Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Modal Window - IFrame
Matej,
Just to be clear - it's not that a modal window in Wicket App A is sourcing
content from Wicket App B. It's that in this scenario Wicket App A has an
generic iframe - not wicket produced - who's src is Wicket App B.
The code here when run from B on modal creation pulls the Wicket.Window from
A which I don't want. I want all modal content to be created in the iframe
document that Wicket App B is sourced in.
Wicket.Window.create = function(settings) {
var win;
if (typeof(settings.src) != undefined Wicket.Browser.isKHTML() ==
false) {
try {
win = window.parent.Wicket.Window;
} catch (ignore) {
}
}
Matej Knopp-2 wrote:
On Wed, Sep 3, 2008 at 10:13 PM, Shaun Thompson [EMAIL PROTECTED] wrote:
I'm currently running into an issue with the wicket modal window.
My situation is this.
Wicket App A contains an IFrame sourcing Wicket App B.
B has an Wicket IFrame modal window on one of it's pages.
When Wicket.Window.create in modal.js is called from B, the
Wicket.Window is pulled from window.parent.Wicket.Window which has
been created in A.
Now the remaining functions called on Wicket.Window are referencing
functions from A modal.js
This becomes a problem when the createDOM in modal.js is called. The
div tag containing the modal html from B is created in A's document.
The iframes src is relative so the content for the modal is not found.
One solution is to have Wicket App B use WebRequestCodingStrategy and
encode all it's url's from relative to absolute. This is not an
optimal solution as I have no control over the multiple wicket apps
that will be sourced in Wicket App A's iframe.
Is there anyway to essentially namespace the Wicket.Window so B does
not pick up A's objects?
I don't think so. And the modal window wasn't really meant to be able
to contain different/multiple applications.
-Matej
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Wicket-Modal-Window---IFrame-tp19297181p19301522.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
