Hi,
As suggested by message subject, you had a problem for testing
AjaxLazyLoadPanel and ModalWindow. You provided a solution for the first
case (great!), but there is nothing in this thread about testing
ModelWindow.
Does your solution apply to ModalWindow too ? Or is there another method ?
NB
, Dec 4, 2009 at 10:16, Bernard Lupin wrote:
Hi again,
After a lot of various tries, I finally found a solution that seems to
work.
On my ModalWindow close button, I don't need javacode anymore, I just
have
this small javascript command in the markup file:
onclick
Hi,
On line 1129 in modal.js, I replaced
iframe src='\/\/:' frameborder=...
with
iframe src='about:blank' frameborder=...
and this solved the problem.
I don't know which browser do not understand about:blank, but both my IE
and my firefox does...
Bernard Lupin wrote:
Hi,
My web site
to solve my problem ?
Regards,
Bernard
Bernard Lupin wrote:
Hi,
On my ModalWindow's close button, I only want to ... close the modal
window. It seems that myWindow.close(target) calls some Ajax request,
which is failing when session is expired.
But if I click on the cross button in the upper
Hi,
On my ModalWindow's close button, I only want to ... close the modal window. It
seems that myWindow.close(target) calls some Ajax request, which is failing
when session is expired.
But if I click on the cross button in the upper right of the modal window,
everything works well : the modal
and if it is present return a properly formatted ajax-response that
contains javascript to redirect to your login page.
-igor
On Tue, Dec 1, 2009 at 1:01 PM, Bernard Lupin beal6...@yahoo.fr wrote:
And I'm using wicket version 1.4.3...
Bernard Lupin wrote:
Hello,
I also have a similar
Hi,
My web site as to run on Firefox and Internet Explorer, so I use IE tab
(https://addons.mozilla.org/fr/firefox/addon/1419) to test it, and for the
first time I see a difference between IE tab and normal IE.
I introduced one ModalWindow (IFrame version) in my page : it works well on IE
and
Hello,
I also have a similar problem : when the session is over, debug shows me that
all my Ajax links receive an html response with my login page, instead of an
xml response, because I have a servlet filter for that.
So wicket says in the wicket ajax debug window ERROR:
And I'm using wicket version 1.4.3...
Bernard Lupin wrote:
Hello,
I also have a similar problem : when the session is over, debug shows me
that all my Ajax links receive an html response with my login page,
instead of an xml response, because I have a servlet filter for that.
So wicket
Hi again,
This question seems to be simple, no ?
Do I have to open a JIRA ?
Bernard
Bernard Lupin wrote:
Hi all,
Components have 3 methods to put information in a feedback panel : info(),
warn() and error().
But in the WicketTester class, there are only 2 asserts available
Thank you very much Igor for your answer.
You're right, this is working even without any code in the onSubmit() method
(in fact I just added one line to manage the visibility of my result
WebMarkupContainer).
Bernard
-Message d'origine-
De : Igor Vaynberg
Hi all,
Components have 3 methods to put information in a feedback panel : info(),
warn() and error().
But in the WicketTester class, there are only 2 asserts available :
assertInfoMessages() and assertErrorMessages().
How can I verify my warning messages ? I can't find an assertWarnMessages.
12 matches
Mail list logo