UPDATE The fix has been released as a part of version 2014R2.
This was a bug in the component. Sorry for inconvenience! It's surprising no one noticed until now. It has been fixed for the next release. Until then, a hotfix is available (contact us if you need it).