You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@wicket.apache.org by Matej Knopp <ma...@gmail.com> on 2008/08/28 01:55:00 UTC

DropDownChoice#onSelectionChanged is called after model is updated.

(tested with trunk)

Shouldn't the method be called *before* the model is updated? At least
that's what the javascript implies. Does anyone know why current
behavior is different?

-Matej

DropDownChoice#onSelectionChanged is called *after* model is updated.

DropDownChoice#onSelectionChanged is called after model is updated.