Hi support,
We have upgraded our Telerik RadEditor to 2015.1.401.45 version.
We are facing issue in IE as mentioned below:
In IE when we select an image and change from Design to HTML mode or try to apply any paragraph style to it, the browser gets unresponsive.
I am able to reproduce the same behaviour with the Telerik demo: http://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx?skin=Default
Can you please help us in solving this issue ?
Regards,
Khush
7 Answers, 1 is accepted

Hello Support,
Is there any update on this?
Regards,
Khush
We are not aware of the experienced problem and, unfortunately, I was not able to reproduce it on my side. Can you please provide a little more details on the exact steps that need to be made in order to reproduce the problem?
- Do you reproduce the issue in all IE versions or only in a specific one?
- Can you take a look at the video from my test and see whether I am not leaving anything out? - screencast
Looking forward to your reply,
Vessy
Telerik

Hi Vessy,
To get a better understanding, please refer to the following videos:
http://screencast.com/t/2qNe7brbrUaU
http://screencast.com/t/jOejQMPKE2DA
I am able to reproduce the issue in IE versions 11, 10, 9.
Regards,
Khush

Hi Vessy,
Is there any update on this?
Regards,
Khush
Тhank you for the provided videos. We have already tracked this issue with another client since my previous reply and it is logged into our bug tracking system. You can track the item progress and vote in order to increase its priority in our feedback portal - http://feedback.telerik.com/Project/108/Feedback/Details/163788.
The only workaround I can suggest you for the moment is to force IE8 compatibility mode of the browser by using the following meta tag:
<
meta
http-equiv
=
"X-UA-Compatible"
content
=
"IE=8"
/>
Regards,
Vessy
Telerik

Hi Vessy,
This has been fixed in Q2 2015 release of Telerik. We have upgraded our Telerik to latest version - 2015.2.729.45
Thanks
Khushboo
Yes, as per your observation and as stated in the item's info this issue was fixed on 15th of July and the fix was included in our 2015 Q2 SP1 release.
Regards,
Vessy
Telerik