I don't actually use this component so out of thin air I'd suggest a) using the default, don't specify event=. b) try
event="valueChange" which is normally the default for UIInput components (and not change, confusingly). So
both suggestions ought to be the same, but that depends on rich:select.
Thanks Brandon, i just tried your suggestion, to no avail though.
Not specifying an event at all shows the same behaviour as specifiying "change", so i assume that is the default event for <rich:select>.
Using "valueChange" does not work:
<f:ajax> 'valueChange' is not a supported event for UISelect. Please specify one of these supported event names: blur, change, click, dblclick, focus, keydown, keypress, keyup, listclick, listdblclick, listhide, listkeydown, listkeypress, listkeyup, listmousedown, listmousemove, listmouseout, listmouseover, listmouseup, listshow, mousedown, mousemove, mouseout, mouseover, mouseup, selectitem.
Update: you reckon i should file a bug report?
Use the "selectitem" event <a4j:ajax event="selectitem".
Javier is right! Use that one!
Thats what i'm doing at the moment. However, like i stated above, the downside is that the event also triggers when the user repeatedly selects the same value he had already selected.
In my case that is acceptable, the performance penalty is negligible, i just wasnt sure if i'm missing something (another event i could listen on for example).
Anyway, thanks for your answers!