I applied the patch to my local version of 1.5.3, and it seems to
solve this issue.
On Fri, Dec 30, 2011 at 12:09 AM, northar josef.anders...@gmail.com wrote:
Yes, tested with 1.5-snapshot now (not extensively), and it seems to work. My
project manager will be glad
--
View this message in
Yes, tested with 1.5-snapshot now (not extensively), and it seems to work. My
project manager will be glad
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Can-t-open-modal-popups-in-ie8-or-under-tp4241461p4245134.html
Sent from the Users forum mailing list archive
Can confirm this bug, and would be glad to see it fixed for 1.5.4, as a lot
of users probaly still use ie8. Does 4241 really fix this?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Can-t-open-modal-popups-in-ie8-or-under-tp4241461p4245024.html
Sent from the Users
I can also confirm this was working in 1.5.0 but not in 1.5.1 - 1.5.3.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Can-t-open-modal-popups-in-ie8-or-under-tp4241461p4245065.html
Sent from the Users forum mailing list archive at Nabble.com.
can you try the snapshot and see if its fixed?
-igor
On Thu, Dec 29, 2011 at 11:42 PM, northar josef.anders...@gmail.com wrote:
I can also confirm this was working in 1.5.0 but not in 1.5.1 - 1.5.3.
--
View this message in context:
I think this is a bug in Wicket 1.5.3.
You cannot open a modal window when using ie8 (possible ie7) if the
context of the page you are opening from has more than one level.
Example,
if your parent page is http://localhost/modaltest, then wicket will
correctly open the modal window in IE,
Sorry, this could be a dupped of WICKET-4241.
-Nelson
On Wed, Dec 28, 2011 at 5:02 PM, Nelson Segura nsegu...@gmail.com wrote:
I think this is a bug in Wicket 1.5.3.
You cannot open a modal window when using ie8 (possible ie7) if the
context of the page you are opening from has more than one
On Thu, Dec 29, 2011 at 3:04 AM, Nelson Segura nsegu...@gmail.com wrote:
Sorry, this could be a dupped of WICKET-4241.
Did you verify that 4241 fixes it ?
-Nelson
On Wed, Dec 28, 2011 at 5:02 PM, Nelson Segura nsegu...@gmail.com wrote:
I think this is a bug in Wicket 1.5.3.
You cannot