RadEditor causes IE8 to crash

[Andrew]

I'm using version 2013.3.1114.40 of the Telerik.Web.UI dll. When a user is typing in text into the RadEditor, IE8 crashes. What is the cause and what is a possible fix?

Thanks!

[Andrew]

I forgot to add my markup: 

<telerik:RadEditor ID="txtBody" runat="server" Width="99%" Height="300" Font-Names="Verdana" Font-Size="Smaller" BackColor="White" EnableResize="false" EnableViewState="true" ViewStateMode="Enabled"  />

[Andrew]

I just discovered that the crashing only occurs if you click 'bold', 'italic', or 'underscore' and then press the backspace key. It was simply crashing for no reason but those three buttons in the editor specifically make the page crash ( in IE8 only ) prior to pressing the backspace key.

[Ianko]

Hi Andrew,

The mentioned problem has been logged for the 2013.3.1114 version and resolved in the 2014 Q1 SP1 release. It is recommended to resolve this issue by upgrading the used Telerik control suite.

Regards,
Ianko
Telerik

 

 

[Łukasz]

Hi,

I'm using version 2013.3.1324.45 of the Telerik.Web.UI dll and I discovered the same bug in the RadEditor. My license ended in Nov 15, 2013
. How can I download this fix?

[Marin Bratanov]

Hi Łukasz,

Generally, to do this, you need to have a valid subscription during the date of the release. I have reopened your ticket on the matter and I have forwarded it to our sales team so they can discuss the available options with you privately.


Regards,

Marin Bratanov
Telerik

 

 

[Łukasz]

hi,

thanks for replay. 
I discovered bug in the lastest version of controls availabe for me in my license. I should download all fix for every bug to this version. I paid for it. This is not my fault that fix is available in newer version.

[Marin Bratanov]

Hello Łukasz,

The bug you have reported with the latest version (currently, Q2 2014 SP1) is fixed and the fix will be available in the Q3 2014 release that is scheduled for the next week.

On the presence of bugs in a given version and their fixes - software does have bugs. It is simply impossible to anticipate the myriad of scenarios a piece of code can be used in, and account for all of them. This becomes even more difficult when there is no limit on the user input like in the editor.

That being said - we do our best to improve the functionality of the controls and fix bugs in every release we have. This is one of the reasons why we have such an aggressive release schedule - 3 major releases per year with at least one service pack for each of them. This means that every couple of months we ship a new version of the suite with a couple of hundred fixes and improvements.

The licensing scheme we employ gives you access to all versions of a major release within the year of purchase. For example, if there is a major release a few days before your subscription expires, you will have access to its service pack(s).

If there are issues in an old version we do try to help (e.g., come up with a workaround or override for that concrete version), but sometimes this is simply impossible. Complex cases often rely on a number of improvements and other fixes that cannot be done in a short timeframe. This new version, however, has a number of new features and controls that may not be part of old subsriptions and this is one of the reasons why fixes can be backdated to old releases and upgrading is usually the best path forward. New versions have many more improvements than just one bug fix. This is the reason why we advise our clients to upgrade often (e.g., with every service pack release), so they will benefit from the latest fixes, new features and controls, while minimizing the chance of encountering issues.

Regards,
Marin Bratanov