This is indeed a bug in the setOptions method, and we have logged it for fixing
. The reason for these inconsistencies in the setOptions method is that it was previously for internal use, but was exposed due to popular demand. Although it has limited functionality, it is still useful to some customers. The API page does not mention these limitations, because we strive to fix them in a timely manner. The recommended approach when setOptions does not support an option is to report it and re-cycle the widget (destroy/init) until it is introduced.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI