You don't need to remove the line. The bug is very difficult to
reproduce, I can't even describe how to trigger it.
The default behavior in newer version will be setCookieName(null), so
the window position will not be persisted. Unless you manually call
setCookieName(someCookieName);
-Matej
Hi,
It seems that quite a lot of people are using ModalWindow lately. I just
want to inform you that there is a bug in modal window that can cause it
to eat all your browser's cookies. The bug is fixed in svn, but not in
the last release (1.2.4).
Fortunately, preventing this bug is fairly
was this in jira? fixed in 1.2.x? if its not could you enter it so it shows
up on 1.2.5 release notes...
thanks,
-igor
On 1/29/07, Matej Knopp [EMAIL PROTECTED] wrote:
Hi,
It seems that quite a lot of people are using ModalWindow lately. I just
want to inform you that there is a bug in
Where can I get more information about this bug? I use ModalWindow for
a few place and this look fine to me, how can I trigger this bug?
By the way, should I remove this line once I update wicket library?
On 1/30/07, Matej Knopp [EMAIL PROTECTED] wrote:
Hi,
It seems that quite a lot of people
