That's too much code to dissect in an email.
Create a quickstart please.
Sven
On 12/18/2013 07:29 PM, Entropy wrote:
This is in one of our Wicket 1.4.7 apps that we have not converted yet. The
problem does not happen in localhost test environments, but does happen on
the server. Moreover,
Yeah, I get that. The problem with that is that I can't reproduce the issue
locally with the FULL APPLICATION, so I am reasonably certain that I won't
be able to reproduce it with a quickstart. It only happens on the server
AND when this panel is visible. I attached the panel as a file if that
New Info:
So I've been promoting over and over, having backed the panel out and slowly
building it back up. When I don't build the buttons in the middle, the page
submits normally. The html for the buttons is:
div id=tabbuttons
button type=button title=Add
I can now add that if only the addSelected button is added, the problem
happens, likewise if only addAll is included. So it appears that any of the
four buttons creates the problem.
add(new AjaxButton(addSelected) {
private static final long
SOLVED
I don't know why i didn't see this earlier, but the issue was using the
button tag instead of input type=button. Somewhere along the line,
someone started using button tags in our shop and we've noticed quirky
behavior from them before (though nothing this quirky). Changed it to input
This is in one of our Wicket 1.4.7 apps that we have not converted yet. The
problem does not happen in localhost test environments, but does happen on
the server. Moreover, the problem only happens when a data condition causes
a particular panel to be visible.
When this panel is visible (and I
