Re: Unable to close ModalWindow 1.4.1
For cross (sub) domain reasons - I am adding document.domain to my page. can't you access your application with http://subdomain.domain.com:8080 at first place? if no, see if you can reach this effect with: http://wicket.apache.org/docs/1.4/org/apache/wicket/request/IRequestCodingStrategy.html at the javadoc says: creating url representations for request targets On Tue, Sep 15, 2009 at 11:17 PM, Ed _ wrote: > > For cross (sub) domain reasons - I am adding document.domain to my page. > > > > Is there a way to make modalwindow / Wickets Ajax links to work with it? > > > > thx > > > From: ed_b...@hotmail.com > > To: users@wicket.apache.org > > Subject: RE: Unable to close ModalWindow 1.4.1 > > Date: Tue, 15 Sep 2009 18:49:03 -0700 > > > > > > > > > > Permission denied for <http://domain.com> to get property Window.Wicket > from <http://subdomain.domain.com:8080>. > > > http://subdomain.domain.com:8080/?wicket:interface=modal-dialog-pagemap:15:: > :: > > Line 265 > > > > wonder why it thinks that the domains are different ? > > > > can I force domain.doc value somehow > > > > thx > > > > > Date: Tue, 15 Sep 2009 21:45:34 -0300 > > > Subject: Re: Unable to close ModalWindow 1.4.1 > > > From: pedros...@gmail.com > > > To: users@wicket.apache.org > > > > > > - I get permission denied exception as reported by firebug. > > > - head section with my javascript > > > > > > The firebug firefox plugging has an javascript console. Execute on him > ( > > > maybe you will not to get permission denied here): > > > alert(Wicket.Window.current) > > > alert(window.parent.Wicket.Window.current) > > > at the end of the javascript operations you report: > > > > > > "At the end of the operations I hide all the divs and then show a div > that > > > has a "close link"" > > > > > > and let us to know what value then have. > > > > > > call the alerts to output the values, > > > > > > On Tue, Sep 15, 2009 at 9:13 PM, Ed _ wrote: > > > > > > > > > > > Thanks for the suggestion. > > > > > > > > I have been using close(target) - unfortunately attached a run when I > was > > > > using both methods. Even with one ajax response appended it doesn't > work. > > > > > > > > New to JS - can you tell me how to test the variables. If I add > > > > > > > > var status = window.parent.Wicket.Window; as part of my JS - I get > > > > permission denied exception as reported by firebug. > > > > > > > > > > > > My html file includes a head section with my javascript and the > markup has > > > > wicket elements viz where the close links are rendered. I have two > such > > > > links - both of which are rendered useless when used in this > configuration - > > > > although the main close button of the modalwindow continues to work. > > > > > > > > thanks > > > > > > > > > Date: Tue, 15 Sep 2009 18:00:47 -0300 > > > > > Subject: Re: Unable to close ModalWindow 1.4.1 > > > > > From: pedros...@gmail.com > > > > > To: users@wicket.apache.org > > > > > > > > > > by close(target) or ModalWindow.close(target) > > > > > --> use close(target), to maintain ModalWindow internal states > updated. > > > > > > > > > > On Tue, Sep 15, 2009 at 5:56 PM, Pedro Santos > > > > > wrote: > > > > > > > > > > > On this ajax response, we can see that the close script was > appended 2 > > > > > > times. Make sure that it appended only once, by close(target) or > > > > > > ModalWindow.close(target). > > > > > > Before click the "close link", in a moment that was causing > trouble, > > > > see if > > > > > > these variables are not null: > > > > > > > > > > > > Wicket.Window.current > > > > > > window.parent.Wicket.Window.current > > > > > > > > > > > > If so, look at what moment they are nullified. The close method > called > > > > on > > > > > > response: > > > > > > win.current.close() > > > > > > depends on these variables. > > > > > > > > > > > > > > &
RE: Unable to close ModalWindow 1.4.1
For cross (sub) domain reasons - I am adding document.domain to my page. Is there a way to make modalwindow / Wickets Ajax links to work with it? thx > From: ed_b...@hotmail.com > To: users@wicket.apache.org > Subject: RE: Unable to close ModalWindow 1.4.1 > Date: Tue, 15 Sep 2009 18:49:03 -0700 > > > > > Permission denied for <http://domain.com> to get property Window.Wicket from > <http://subdomain.domain.com:8080>. > http://subdomain.domain.com:8080/?wicket:interface=modal-dialog-pagemap:15 > Line 265 > > wonder why it thinks that the domains are different ? > > can I force domain.doc value somehow > > thx > > > Date: Tue, 15 Sep 2009 21:45:34 -0300 > > Subject: Re: Unable to close ModalWindow 1.4.1 > > From: pedros...@gmail.com > > To: users@wicket.apache.org > > > > - I get permission denied exception as reported by firebug. > > - head section with my javascript > > > > The firebug firefox plugging has an javascript console. Execute on him ( > > maybe you will not to get permission denied here): > > alert(Wicket.Window.current) > > alert(window.parent.Wicket.Window.current) > > at the end of the javascript operations you report: > > > > "At the end of the operations I hide all the divs and then show a div that > > has a "close link"" > > > > and let us to know what value then have. > > > > call the alerts to output the values, > > > > On Tue, Sep 15, 2009 at 9:13 PM, Ed _ wrote: > > > > > > > > Thanks for the suggestion. > > > > > > I have been using close(target) - unfortunately attached a run when I was > > > using both methods. Even with one ajax response appended it doesn't work. > > > > > > New to JS - can you tell me how to test the variables. If I add > > > > > > var status = window.parent.Wicket.Window; as part of my JS - I get > > > permission denied exception as reported by firebug. > > > > > > > > > My html file includes a head section with my javascript and the markup has > > > wicket elements viz where the close links are rendered. I have two such > > > links - both of which are rendered useless when used in this > > > configuration - > > > although the main close button of the modalwindow continues to work. > > > > > > thanks > > > > > > > Date: Tue, 15 Sep 2009 18:00:47 -0300 > > > > Subject: Re: Unable to close ModalWindow 1.4.1 > > > > From: pedros...@gmail.com > > > > To: users@wicket.apache.org > > > > > > > > by close(target) or ModalWindow.close(target) > > > > --> use close(target), to maintain ModalWindow internal states updated. > > > > > > > > On Tue, Sep 15, 2009 at 5:56 PM, Pedro Santos > > > wrote: > > > > > > > > > On this ajax response, we can see that the close script was appended 2 > > > > > times. Make sure that it appended only once, by close(target) or > > > > > ModalWindow.close(target). > > > > > Before click the "close link", in a moment that was causing trouble, > > > see if > > > > > these variables are not null: > > > > > > > > > > Wicket.Window.current > > > > > window.parent.Wicket.Window.current > > > > > > > > > > If so, look at what moment they are nullified. The close method called > > > on > > > > > response: > > > > > win.current.close() > > > > > depends on these variables. > > > > > > > > > > > > > > > On Tue, Sep 15, 2009 at 4:54 PM, Ed _ wrote: > > > > > > > > > >> > > > > >> > > > > >> Looking for hints to debug the situation I am in. Thanks. > > > > >> > > > > >> Using wickets 1.4.1 > > > > >> > > > > >> I have tried a simple scenario - opening a page in a modal window > > > > >> and > > > > >> then using a link in the page to close the window. Works fine. > > > > >> > > > > >> Now I am opening a more complicated page with its own javascript - > > > > >> performing a bunch of operations on that page using js while it is > > > opened in > > > > >> a modal window. At the end of the operations I hide all the divs and > > > then > > > &g
RE: Unable to close ModalWindow 1.4.1
Permission denied for <http://domain.com> to get property Window.Wicket from <http://subdomain.domain.com:8080>. http://subdomain.domain.com:8080/?wicket:interface=modal-dialog-pagemap:15 Line 265 wonder why it thinks that the domains are different ? can I force domain.doc value somehow thx > Date: Tue, 15 Sep 2009 21:45:34 -0300 > Subject: Re: Unable to close ModalWindow 1.4.1 > From: pedros...@gmail.com > To: users@wicket.apache.org > > - I get permission denied exception as reported by firebug. > - head section with my javascript > > The firebug firefox plugging has an javascript console. Execute on him ( > maybe you will not to get permission denied here): > alert(Wicket.Window.current) > alert(window.parent.Wicket.Window.current) > at the end of the javascript operations you report: > > "At the end of the operations I hide all the divs and then show a div that > has a "close link"" > > and let us to know what value then have. > > call the alerts to output the values, > > On Tue, Sep 15, 2009 at 9:13 PM, Ed _ wrote: > > > > > Thanks for the suggestion. > > > > I have been using close(target) - unfortunately attached a run when I was > > using both methods. Even with one ajax response appended it doesn't work. > > > > New to JS - can you tell me how to test the variables. If I add > > > > var status = window.parent.Wicket.Window; as part of my JS - I get > > permission denied exception as reported by firebug. > > > > > > My html file includes a head section with my javascript and the markup has > > wicket elements viz where the close links are rendered. I have two such > > links - both of which are rendered useless when used in this configuration - > > although the main close button of the modalwindow continues to work. > > > > thanks > > > > > Date: Tue, 15 Sep 2009 18:00:47 -0300 > > > Subject: Re: Unable to close ModalWindow 1.4.1 > > > From: pedros...@gmail.com > > > To: users@wicket.apache.org > > > > > > by close(target) or ModalWindow.close(target) > > > --> use close(target), to maintain ModalWindow internal states updated. > > > > > > On Tue, Sep 15, 2009 at 5:56 PM, Pedro Santos > > wrote: > > > > > > > On this ajax response, we can see that the close script was appended 2 > > > > times. Make sure that it appended only once, by close(target) or > > > > ModalWindow.close(target). > > > > Before click the "close link", in a moment that was causing trouble, > > see if > > > > these variables are not null: > > > > > > > > Wicket.Window.current > > > > window.parent.Wicket.Window.current > > > > > > > > If so, look at what moment they are nullified. The close method called > > on > > > > response: > > > > win.current.close() > > > > depends on these variables. > > > > > > > > > > > > On Tue, Sep 15, 2009 at 4:54 PM, Ed _ wrote: > > > > > > > >> > > > >> > > > >> Looking for hints to debug the situation I am in. Thanks. > > > >> > > > >> Using wickets 1.4.1 > > > >> > > > >> I have tried a simple scenario - opening a page in a modal window and > > > >> then using a link in the page to close the window. Works fine. > > > >> > > > >> Now I am opening a more complicated page with its own javascript - > > > >> performing a bunch of operations on that page using js while it is > > opened in > > > >> a modal window. At the end of the operations I hide all the divs and > > then > > > >> show a div that has a "close link" > > > >> > > > >> The link does not close the modal window - I see the request coming to > > the > > > >> server I call close(target) tried ModalWindow.close(target) too but > > nothing > > > >> happens. > > > >> > > > >> The window closes with the X close button on the top right. > > > >> > > > >> the wicket debug shows the operation / at least being able to fetch > > the > > > >> code to shut the window down succeeding . > > > >> > > > >> > > > >> > > http://hostname/?wicket:interface=mymodalWindow:3:doneInstall::IBehaviorListener:0:&random=0.3818687947575885 > > > >> > > > >> > > >> encoding="UTF-8"?> > > > >> > > > >> _ > > > >> Hotmail: Free, trusted and rich email service. > > > >> http://clk.atdmt.com/GBL/go/171222984/direct/01/ > > > >> > > > > > > > > > > > > _ > > Bing brings you health info from trusted sources. > > > > http://www.bing.com/search?q=pet+allergy&form=MHEINA&publ=WLHMTAG&crea=TXT_MHEINA_Health_Health_PetAllergy_1x1 _ Bing brings you health info from trusted sources. http://www.bing.com/search?q=pet+allergy&form=MHEINA&publ=WLHMTAG&crea=TXT_MHEINA_Health_Health_PetAllergy_1x1
RE: Unable to close ModalWindow 1.4.1
Ok I added this to the html alert(window.parent.Wicket.Window.current); of my simple page example and the alert poped up with [object Object] When I add it to my actual page - I get permission denied. :( alert(Wicket.Window.current) - shows up as an error - undefined in the test page. Thanks > Date: Tue, 15 Sep 2009 21:45:34 -0300 > Subject: Re: Unable to close ModalWindow 1.4.1 > From: pedros...@gmail.com > To: users@wicket.apache.org > > - I get permission denied exception as reported by firebug. > - head section with my javascript > > The firebug firefox plugging has an javascript console. Execute on him ( > maybe you will not to get permission denied here): > alert(Wicket.Window.current) > alert(window.parent.Wicket.Window.current) > at the end of the javascript operations you report: > > "At the end of the operations I hide all the divs and then show a div that > has a "close link"" > > and let us to know what value then have. > > call the alerts to output the values, > > On Tue, Sep 15, 2009 at 9:13 PM, Ed _ wrote: > > > > > Thanks for the suggestion. > > > > I have been using close(target) - unfortunately attached a run when I was > > using both methods. Even with one ajax response appended it doesn't work. > > > > New to JS - can you tell me how to test the variables. If I add > > > > var status = window.parent.Wicket.Window; as part of my JS - I get > > permission denied exception as reported by firebug. > > > > > > My html file includes a head section with my javascript and the markup has > > wicket elements viz where the close links are rendered. I have two such > > links - both of which are rendered useless when used in this configuration - > > although the main close button of the modalwindow continues to work. > > > > thanks > > > > > Date: Tue, 15 Sep 2009 18:00:47 -0300 > > > Subject: Re: Unable to close ModalWindow 1.4.1 > > > From: pedros...@gmail.com > > > To: users@wicket.apache.org > > > > > > by close(target) or ModalWindow.close(target) > > > --> use close(target), to maintain ModalWindow internal states updated. > > > > > > On Tue, Sep 15, 2009 at 5:56 PM, Pedro Santos > > wrote: > > > > > > > On this ajax response, we can see that the close script was appended 2 > > > > times. Make sure that it appended only once, by close(target) or > > > > ModalWindow.close(target). > > > > Before click the "close link", in a moment that was causing trouble, > > see if > > > > these variables are not null: > > > > > > > > Wicket.Window.current > > > > window.parent.Wicket.Window.current > > > > > > > > If so, look at what moment they are nullified. The close method called > > on > > > > response: > > > > win.current.close() > > > > depends on these variables. > > > > > > > > > > > > On Tue, Sep 15, 2009 at 4:54 PM, Ed _ wrote: > > > > > > > >> > > > >> > > > >> Looking for hints to debug the situation I am in. Thanks. > > > >> > > > >> Using wickets 1.4.1 > > > >> > > > >> I have tried a simple scenario - opening a page in a modal window and > > > >> then using a link in the page to close the window. Works fine. > > > >> > > > >> Now I am opening a more complicated page with its own javascript - > > > >> performing a bunch of operations on that page using js while it is > > opened in > > > >> a modal window. At the end of the operations I hide all the divs and > > then > > > >> show a div that has a "close link" > > > >> > > > >> The link does not close the modal window - I see the request coming to > > the > > > >> server I call close(target) tried ModalWindow.close(target) too but > > nothing > > > >> happens. > > > >> > > > >> The window closes with the X close button on the top right. > > > >> > > > >> the wicket debug shows the operation / at least being able to fetch > > the > > > >> code to shut the window down succeeding . > > > >> > > > >> > > > >> > > http://hostname/?wicket:interface=mymodalWindow:3:doneInstall::IBehaviorListener:0:&random=0.3818687947575885 > > > >> > > > >> > > >> encoding="UTF-8"?> > > > >> > > > >> _ > > > >> Hotmail: Free, trusted and rich email service. > > > >> http://clk.atdmt.com/GBL/go/171222984/direct/01/ > > > >> > > > > > > > > > > > > _ > > Bing brings you health info from trusted sources. > > > > http://www.bing.com/search?q=pet+allergy&form=MHEINA&publ=WLHMTAG&crea=TXT_MHEINA_Health_Health_PetAllergy_1x1 _ Hotmail: Powerful Free email with security by Microsoft. http://clk.atdmt.com/GBL/go/171222986/direct/01/
Re: Unable to close ModalWindow 1.4.1
- I get permission denied exception as reported by firebug. - head section with my javascript The firebug firefox plugging has an javascript console. Execute on him ( maybe you will not to get permission denied here): alert(Wicket.Window.current) alert(window.parent.Wicket.Window.current) at the end of the javascript operations you report: "At the end of the operations I hide all the divs and then show a div that has a "close link"" and let us to know what value then have. call the alerts to output the values, On Tue, Sep 15, 2009 at 9:13 PM, Ed _ wrote: > > Thanks for the suggestion. > > I have been using close(target) - unfortunately attached a run when I was > using both methods. Even with one ajax response appended it doesn't work. > > New to JS - can you tell me how to test the variables. If I add > > var status = window.parent.Wicket.Window; as part of my JS - I get > permission denied exception as reported by firebug. > > > My html file includes a head section with my javascript and the markup has > wicket elements viz where the close links are rendered. I have two such > links - both of which are rendered useless when used in this configuration - > although the main close button of the modalwindow continues to work. > > thanks > > > Date: Tue, 15 Sep 2009 18:00:47 -0300 > > Subject: Re: Unable to close ModalWindow 1.4.1 > > From: pedros...@gmail.com > > To: users@wicket.apache.org > > > > by close(target) or ModalWindow.close(target) > > --> use close(target), to maintain ModalWindow internal states updated. > > > > On Tue, Sep 15, 2009 at 5:56 PM, Pedro Santos > wrote: > > > > > On this ajax response, we can see that the close script was appended 2 > > > times. Make sure that it appended only once, by close(target) or > > > ModalWindow.close(target). > > > Before click the "close link", in a moment that was causing trouble, > see if > > > these variables are not null: > > > > > > Wicket.Window.current > > > window.parent.Wicket.Window.current > > > > > > If so, look at what moment they are nullified. The close method called > on > > > response: > > > win.current.close() > > > depends on these variables. > > > > > > > > > On Tue, Sep 15, 2009 at 4:54 PM, Ed _ wrote: > > > > > >> > > >> > > >> Looking for hints to debug the situation I am in. Thanks. > > >> > > >> Using wickets 1.4.1 > > >> > > >> I have tried a simple scenario - opening a page in a modal window and > > >> then using a link in the page to close the window. Works fine. > > >> > > >> Now I am opening a more complicated page with its own javascript - > > >> performing a bunch of operations on that page using js while it is > opened in > > >> a modal window. At the end of the operations I hide all the divs and > then > > >> show a div that has a "close link" > > >> > > >> The link does not close the modal window - I see the request coming to > the > > >> server I call close(target) tried ModalWindow.close(target) too but > nothing > > >> happens. > > >> > > >> The window closes with the X close button on the top right. > > >> > > >> the wicket debug shows the operation / at least being able to fetch > the > > >> code to shut the window down succeeding . > > >> > > >> > > >> > http://hostname/?wicket:interface=mymodalWindow:3:doneInstall::IBehaviorListener:0:&random=0.3818687947575885 > > >> > > >> > >> encoding="UTF-8"?> > > >> > > >> _ > > >> Hotmail: Free, trusted and rich email service. > > >> http://clk.atdmt.com/GBL/go/171222984/direct/01/ > > >> > > > > > > > > _ > Bing brings you health info from trusted sources. > > http://www.bing.com/search?q=pet+allergy&form=MHEINA&publ=WLHMTAG&crea=TXT_MHEINA_Health_Health_PetAllergy_1x1
RE: Unable to close ModalWindow 1.4.1
Here is the wicket AJax Debug INFO: focus set on cancelUpdatea8INFO: Using XMLHttpRequest transportINFO: INFO: Initiating Ajax GET request on ?wicket:interface=modal-dialog-pagemap:26:cancelUpdate::IBehaviorListener:0:&random=0.5391539823210829INFO: Invoking pre-call handler(s)...INFO: Received ajax response (541 characters)INFO: INFO: Response parsed. Now invoking steps...INFO: Response processed successfully.INFO: Invoking post-call handler(s)...INFO: refocus last focused component not needed/allowedINFO: focus removed from cancelUpdatea8 > Date: Tue, 15 Sep 2009 18:00:47 -0300 > Subject: Re: Unable to close ModalWindow 1.4.1 > From: pedros...@gmail.com > To: users@wicket.apache.org > > by close(target) or ModalWindow.close(target) > --> use close(target), to maintain ModalWindow internal states updated. > > On Tue, Sep 15, 2009 at 5:56 PM, Pedro Santos wrote: > > > On this ajax response, we can see that the close script was appended 2 > > times. Make sure that it appended only once, by close(target) or > > ModalWindow.close(target). > > Before click the "close link", in a moment that was causing trouble, see if > > these variables are not null: > > > > Wicket.Window.current > > window.parent.Wicket.Window.current > > > > If so, look at what moment they are nullified. The close method called on > > response: > > win.current.close() > > depends on these variables. > > > > > > On Tue, Sep 15, 2009 at 4:54 PM, Ed _ wrote: > > > >> > >> > >> Looking for hints to debug the situation I am in. Thanks. > >> > >> Using wickets 1.4.1 > >> > >> I have tried a simple scenario - opening a page in a modal window and > >> then using a link in the page to close the window. Works fine. > >> > >> Now I am opening a more complicated page with its own javascript - > >> performing a bunch of operations on that page using js while it is opened > >> in > >> a modal window. At the end of the operations I hide all the divs and then > >> show a div that has a "close link" > >> > >> The link does not close the modal window - I see the request coming to the > >> server I call close(target) tried ModalWindow.close(target) too but nothing > >> happens. > >> > >> The window closes with the X close button on the top right. > >> > >> the wicket debug shows the operation / at least being able to fetch the > >> code to shut the window down succeeding . > >> > >> > >> http://hostname/?wicket:interface=mymodalWindow:3:doneInstall::IBehaviorListener:0:&random=0.3818687947575885 > >> > >> >> encoding="UTF-8"?> > >> > >> _ > >> Hotmail: Free, trusted and rich email service. > >> http://clk.atdmt.com/GBL/go/171222984/direct/01/ > >> > > > > _ Bing brings you health info from trusted sources. http://www.bing.com/search?q=pet+allergy&form=MHEINA&publ=WLHMTAG&crea=TXT_MHEINA_Health_Health_PetAllergy_1x1
RE: Unable to close ModalWindow 1.4.1
Thanks for the suggestion. I have been using close(target) - unfortunately attached a run when I was using both methods. Even with one ajax response appended it doesn't work. New to JS - can you tell me how to test the variables. If I add var status = window.parent.Wicket.Window; as part of my JS - I get permission denied exception as reported by firebug. My html file includes a head section with my javascript and the markup has wicket elements viz where the close links are rendered. I have two such links - both of which are rendered useless when used in this configuration - although the main close button of the modalwindow continues to work. thanks > Date: Tue, 15 Sep 2009 18:00:47 -0300 > Subject: Re: Unable to close ModalWindow 1.4.1 > From: pedros...@gmail.com > To: users@wicket.apache.org > > by close(target) or ModalWindow.close(target) > --> use close(target), to maintain ModalWindow internal states updated. > > On Tue, Sep 15, 2009 at 5:56 PM, Pedro Santos wrote: > > > On this ajax response, we can see that the close script was appended 2 > > times. Make sure that it appended only once, by close(target) or > > ModalWindow.close(target). > > Before click the "close link", in a moment that was causing trouble, see if > > these variables are not null: > > > > Wicket.Window.current > > window.parent.Wicket.Window.current > > > > If so, look at what moment they are nullified. The close method called on > > response: > > win.current.close() > > depends on these variables. > > > > > > On Tue, Sep 15, 2009 at 4:54 PM, Ed _ wrote: > > > >> > >> > >> Looking for hints to debug the situation I am in. Thanks. > >> > >> Using wickets 1.4.1 > >> > >> I have tried a simple scenario - opening a page in a modal window and > >> then using a link in the page to close the window. Works fine. > >> > >> Now I am opening a more complicated page with its own javascript - > >> performing a bunch of operations on that page using js while it is opened > >> in > >> a modal window. At the end of the operations I hide all the divs and then > >> show a div that has a "close link" > >> > >> The link does not close the modal window - I see the request coming to the > >> server I call close(target) tried ModalWindow.close(target) too but nothing > >> happens. > >> > >> The window closes with the X close button on the top right. > >> > >> the wicket debug shows the operation / at least being able to fetch the > >> code to shut the window down succeeding . > >> > >> > >> http://hostname/?wicket:interface=mymodalWindow:3:doneInstall::IBehaviorListener:0:&random=0.3818687947575885 > >> > >> >> encoding="UTF-8"?> > >> > >> _ > >> Hotmail: Free, trusted and rich email service. > >> http://clk.atdmt.com/GBL/go/171222984/direct/01/ > >> > > > > _ Bing brings you health info from trusted sources. http://www.bing.com/search?q=pet+allergy&form=MHEINA&publ=WLHMTAG&crea=TXT_MHEINA_Health_Health_PetAllergy_1x1
Re: Unable to close ModalWindow 1.4.1
by close(target) or ModalWindow.close(target) --> use close(target), to maintain ModalWindow internal states updated. On Tue, Sep 15, 2009 at 5:56 PM, Pedro Santos wrote: > On this ajax response, we can see that the close script was appended 2 > times. Make sure that it appended only once, by close(target) or > ModalWindow.close(target). > Before click the "close link", in a moment that was causing trouble, see if > these variables are not null: > > Wicket.Window.current > window.parent.Wicket.Window.current > > If so, look at what moment they are nullified. The close method called on > response: > win.current.close() > depends on these variables. > > > On Tue, Sep 15, 2009 at 4:54 PM, Ed _ wrote: > >> >> >> Looking for hints to debug the situation I am in. Thanks. >> >> Using wickets 1.4.1 >> >> I have tried a simple scenario - opening a page in a modal window and >> then using a link in the page to close the window. Works fine. >> >> Now I am opening a more complicated page with its own javascript - >> performing a bunch of operations on that page using js while it is opened in >> a modal window. At the end of the operations I hide all the divs and then >> show a div that has a "close link" >> >> The link does not close the modal window - I see the request coming to the >> server I call close(target) tried ModalWindow.close(target) too but nothing >> happens. >> >> The window closes with the X close button on the top right. >> >> the wicket debug shows the operation / at least being able to fetch the >> code to shut the window down succeeding . >> >> >> http://hostname/?wicket:interface=mymodalWindow:3:doneInstall::IBehaviorListener:0:&random=0.3818687947575885 >> >> > encoding="UTF-8"?> >> >> _ >> Hotmail: Free, trusted and rich email service. >> http://clk.atdmt.com/GBL/go/171222984/direct/01/ >> > >
Re: Unable to close ModalWindow 1.4.1
On this ajax response, we can see that the close script was appended 2 times. Make sure that it appended only once, by close(target) or ModalWindow.close(target). Before click the "close link", in a moment that was causing trouble, see if these variables are not null: Wicket.Window.current window.parent.Wicket.Window.current If so, look at what moment they are nullified. The close method called on response: win.current.close() depends on these variables. On Tue, Sep 15, 2009 at 4:54 PM, Ed _ wrote: > > > Looking for hints to debug the situation I am in. Thanks. > > Using wickets 1.4.1 > > I have tried a simple scenario - opening a page in a modal window and then > using a link in the page to close the window. Works fine. > > Now I am opening a more complicated page with its own javascript - > performing a bunch of operations on that page using js while it is opened in > a modal window. At the end of the operations I hide all the divs and then > show a div that has a "close link" > > The link does not close the modal window - I see the request coming to the > server I call close(target) tried ModalWindow.close(target) too but nothing > happens. > > The window closes with the X close button on the top right. > > the wicket debug shows the operation / at least being able to fetch the > code to shut the window down succeeding . > > > http://hostname/?wicket:interface=mymodalWindow:3:doneInstall::IBehaviorListener:0:&random=0.3818687947575885 > > > > _ > Hotmail: Free, trusted and rich email service. > http://clk.atdmt.com/GBL/go/171222984/direct/01/ >
Unable to close ModalWindow 1.4.1
Looking for hints to debug the situation I am in. Thanks. Using wickets 1.4.1 I have tried a simple scenario - opening a page in a modal window and then using a link in the page to close the window. Works fine. Now I am opening a more complicated page with its own javascript - performing a bunch of operations on that page using js while it is opened in a modal window. At the end of the operations I hide all the divs and then show a div that has a "close link" The link does not close the modal window - I see the request coming to the server I call close(target) tried ModalWindow.close(target) too but nothing happens. The window closes with the X close button on the top right. the wicket debug shows the operation / at least being able to fetch the code to shut the window down succeeding . http://hostname/?wicket:interface=mymodalWindow:3:doneInstall::IBehaviorListener:0:&random=0.3818687947575885 _ Hotmail: Free, trusted and rich email service. http://clk.atdmt.com/GBL/go/171222984/direct/01/
