Anonymous wrote:

Null values should also sent to a server!
If user now clears that select to "" value and lets says clicks another select-component. Previous select component still shows "" but Select.getValue returns "123".
 

That is true - this sounds like a potential bug. 

Anonymous wrote:

thanks a lot, I appreciate that!
What do you suspect, how long might it take before there is new 4.x.x build with these bugs fixed?
I'm just considering whether to copy Select and alter it myself or wait for official fixes. 

Both of these bugs are easy to fix. I scheduled Toolkit version 4.0.4 for next week, we'll postpone some other changesets for 4.0.5 which comes out most likely within few weeks after 4.0.4 is out, but this minor inconvenience for us.