Hi,
I'm having same errors in IE10 and Opera. Chrome and Firefox don't do this
(neither does IE always, but almost always it does). Wicket versions are 1.5.8
and 6.7.0
My case is a modal window that contains a panel with Image
(org.apache.wicket.markup.html.image.Image)
When modal window
Hi,
On Fri, May 24, 2013 at 10:47 AM, Mikko Pukki
mikko.pu...@syncrontech.comwrote:
Hi,
I'm having same errors in IE10 and Opera. Chrome and Firefox don't do this
(neither does IE always, but almost always it does). Wicket versions are
1.5.8 and 6.7.0
My case is a modal window that
There is an open ticket in our Jira about this problem -
https://issues.apache.org/jira/browse/WICKET-3869.
It has a quickstart too.
You may try to debug it if it reproduces with your setup.
On Fri, May 24, 2013 at 11:29 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
On Fri, May 24,
After upgrading to Wicket 6, I am getting too many of exceptions
like the ones below. They 'happen' either when delivering static
contents, like Javascript files (via resource references) or even
media contents like images or movies which are written into the
response. I've appended two
Hi,
Does these errors happen in any browser or only in IE ?
I remember such problem in IE - the browser renders the page in modeX and
during download of the resources switches to modeY, so it closes the opened
connections and downloads the resource again.
Either modeX or modeY is QuirksMode.
The
On Tue, April 16, 2013, Martin Grigorov wrote:
Does these errors happen in any browser or only in IE ?
I remember such problem in IE - the browser renders the page in modeX and
during download of the resources switches to modeY, so it closes the opened
connections and downloads the resource
On Tue, Apr 16, 2013 at 2:56 PM, Martin Dietze d...@fh-wedel.de wrote:
On Tue, April 16, 2013, Martin Grigorov wrote:
Does these errors happen in any browser or only in IE ?
I remember such problem in IE - the browser renders the page in modeX and
during download of the resources switches
On Tue, April 16, 2013, Martin Grigorov wrote:
I'm not sure what redirect you mean.
I was referring to the fact that the error page was called here:
| ERROR 2013-04-15T12:29:35 [http-thread-pool-443-(36)]
my.company.app.ui.pages.error.ErrorPage [USER.8619]
