I'm using a kendo grid with a toolbar with buttons that might be disabled (and using the class k-state-disabled). After updating version of kendo the disabled buttons got less distinctive and - possible worst of all - started to react to hover.
After looking further into this I noticed that the k-secondary class that kendo adds to the grid wrapper is mainly responsible for this behavior as shown in this jsfiddle:
http://jsfiddle.net/DLezC/
What is the reason for using the k-secondary on the grid and why does it affect the disabled buttons. Is this to be considered as a bug? Is there a better way to accomplice the disabled effect?
After looking further into this I noticed that the k-secondary class that kendo adds to the grid wrapper is mainly responsible for this behavior as shown in this jsfiddle:
http://jsfiddle.net/DLezC/
What is the reason for using the k-secondary on the grid and why does it affect the disabled buttons. Is this to be considered as a bug? Is there a better way to accomplice the disabled effect?
1 Answer, 1 is accepted
0
Hi Peter,
We are aware of this problem and it will be fixed in the future. In the meantime, please remove the k-secondary class. Its goal is to support two types of button looks, but has undesired side effects. Sorry about that.
Regards,
Dimo
Telerik
We are aware of this problem and it will be fixed in the future. In the meantime, please remove the k-secondary class. Its goal is to support two types of button looks, but has undesired side effects. Sorry about that.
Regards,
Dimo
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!