We did research on this topic, but we could not change the current behavior of the RadInputManager
Since the manager creates only one RadInputComponent
for each TextBoxSetting
, applying different styles is not possible.
Persisting the original class for each Input would mean to create an object for each one, and this is against the idea of the InputManager, which is used to apply the same settings for all inputs for given setting. Storing different settings would cause lot of performance penalty what we wont to avoid. On the other hand storing all settings inside the RadInputComponent
will cause problem during partial updates when you update only some of the TextBoxes. The this case the InputComponent will have old values after the update which would be not suitable for general usage.
The manager overrides the CssClass
property of the asp:TextBox
, so to apply it's classes during the rendering properly, and to matches with the classes that are applied dynamically ClientSide.
As a workaround you could create different TextBoxSettings
for your inputs, if you have to group them in several groups. Or if you need to recognize each of them separately, it would be best to select them by ID instead of class.
All the best,
the Telerik team
Sharpen your .NET Ninja skills
! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>