Completed
Last Updated: 11 Aug 2016 14:04 by ADMIN
Kevin
Created on: 07 Aug 2012 08:03
Category: BusyIndicator
Type: Bug Report
4
Content of the RadBusyIndicator is disabled right away even if DisplayAfter is set
The title is accurate but the description is pretty far off. The problem is that a RadBusyIndicator with a DisplayAfter of 1.5 seconds and IsBusy=true  will initially set its contents to disabled and then enable the contents when IsBusy becomes false.  The
1 comment
ADMIN
Telerik Admin
Posted on: 07 Aug 2012 15:53
Content of RadBusyIndicator should be disabled after the DisplayAfter time has expired.

Available in LIB version 2015.3.1207,  it will be also available in the 2016 Q1 release.