Hi Myriam,
yes, the fd;on-value-changed is the right way to do it.
The typical case is the state/region/province/town selections, where
selecting a state must populate the regions dropdown with the right
regions and so on. This is done with an fd:on-value-changed listener
that populates the other selection list with proper data. Simply, add
the <fi:styling submit-on-change="true"/> to the field in the template,
so that the form will be submitted and the server side listener has the
possibility to run when the user selects a value in the drop down.
Also consider that on some browsers (internet explorer) the change event
is not triggered until the user clicks away from the field. This is done
to avoid generating a lot of events while the user is simply browsing
the available options, or typing the first few letters in a text field.
This happens on some fields, like radio and check buttons, but may
happen also on drop downs, depends on browsers.
Myriam Delperier wrote:
Simone Gianni wrote:
| | Hi Myriam,
| | the fd:on-value-changed is a SERVER SIDE event handler. So it's
| | triggered when the form is submitted by the browser. You can force
| | the browser to submit the form whenever a given widget value is
| | changed | | using the <fi:styling submit-on-change="true"/> in the
form
| | template (it should do this automatically if there is a listener,
| | but since it's not working in your case you can make it explicit).
ok , so that's not the solution of my problem.
i've got 2 lists in my form
and the uri of the second one depends of the value of the first one
how can i do this ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
