Hello,
I have a multiline RadTextBox on my page:
Later, this textbox is made read-only (from code-behind - depending on permissions of user). Under Chrome and Firefox everything works well - even though the textbox is disabled, I can use scrollbar and read all the text. Unfortunately, under IE (both IE8 and IE9) the scrollbar is shown but it's not enabled.
Is there any way to make it usable?
Thank you in advance.
I have a multiline RadTextBox on my page:
<telerik:RadTextBox ID="DescriptionTextBox" TextMode="MultiLine" runat="server" Width="100%" Height="150px" />Later, this textbox is made read-only (from code-behind - depending on permissions of user). Under Chrome and Firefox everything works well - even though the textbox is disabled, I can use scrollbar and read all the text. Unfortunately, under IE (both IE8 and IE9) the scrollbar is shown but it's not enabled.
Is there any way to make it usable?
Thank you in advance.
2 Answers, 1 is accepted
0
Hi Pawel,
Please note that the described behaviour is actually browser behaviour and this is how the IE works even regular asp TextBox is used. This is a limitation in IE on which the disabled inputs disable their scrolling also. Possible approach in this case is to use the ReadOnly property instead of disabling the control.
Regards,
Maria Ilieva
the Telerik team
Please note that the described behaviour is actually browser behaviour and this is how the IE works even regular asp TextBox is used. This is a limitation in IE on which the disabled inputs disable their scrolling also. Possible approach in this case is to use the ReadOnly property instead of disabling the control.
Regards,
Maria Ilieva
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
0
pawelg
Top achievements
Rank 1
Rank 1
answered on 04 Oct 2012, 01:11 PM
Hello Maria,
Thank you for your answer, I didn't know about this limitation. Now it works perfectly with ReadOnly set to false.
Best regards,
Pawel
Thank you for your answer, I didn't know about this limitation. Now it works perfectly with ReadOnly set to false.
Best regards,
Pawel