Going a bit deeper into the problem, it looks like wicket picks up the
z-index values in an arbitrary way. The components do not integrate enough
to figure out the correct z-index values. For instance, the date picker is
set at z-index 1000, while the modal window's mask is set to 2000 and so on.
I am not sure why these particular z-index values are picked, but they sure
not working together. A better approach perhaps would be to derive the
z-index value from peer components in the page in a relative manner rather
than picking absolute values.
View this message in context: 
Sent from the Wicket - User forum at Nabble.com.

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Wicket-user mailing list

Reply via email to