Hello Grant,
In Q2 2015 (v2015.2.624+), we changed the widgets initialization approach and thus boost the initialization time. Basically, before the widgets were initialized with setTimeout, which now is removed. The result is that the widgets are initialized instantly and they don't wait for the HTML to be modified by AngularJS.
Generally speaking, scenarios where the id/name fields were modified with Angular templates ({{ field }}) are not supported. It worked by chance because of the used setTimeout.
The best solution in this case is to avoid using "{{ }}" syntax in the id/name attributes. If dynamic update of ID fields is a must, then you will need to force the widgets initialization delay manually. One possible option is to use k-ng-delay mapped to some field that is updated with setTimeout.
Regards,
Georgi Krustev
Telerik
In Q2 2015 (v2015.2.624+), we changed the widgets initialization approach and thus boost the initialization time. Basically, before the widgets were initialized with setTimeout, which now is removed. The result is that the widgets are initialized instantly and they don't wait for the HTML to be modified by AngularJS.
Generally speaking, scenarios where the id/name fields were modified with Angular templates ({{ field }}) are not supported. It worked by chance because of the used setTimeout.
The best solution in this case is to avoid using "{{ }}" syntax in the id/name attributes. If dynamic update of ID fields is a must, then you will need to force the widgets initialization delay manually. One possible option is to use k-ng-delay mapped to some field that is updated with setTimeout.
Regards,
Georgi Krustev
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!






