yes, Sven.
it's the same issue of wicket-4279
https://issues.apache.org/jira/browse/WICKET-4279
I'll download wicket 1.5.4 after release, thank you!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/questions-about-CheckGroupSelector-s-behavior-tp4291374p4291630.html
WICKET-4279 ?
Am 13.01.2012 05:32, schrieb rolandpeng:
CheckGroupSelector is very useful to select all/none, but I found there is
one condition that the behavior of CheckGroupSelector becomes strange. I'm
not sure whether it's a bug or not.
When the CheckGroup contains more than two check items
CheckGroupSelector is very useful to select all/none, but I found there is
one condition that the behavior of CheckGroupSelector becomes strange. I'm
not sure whether it's a bug or not.
When the CheckGroup contains more than two check items, it's fine for any
function.
But when it contains only on
