This is the skeleton of a template we have to use. In Firefox and IE it's not causing any problems. But there is major slowdown when it's in Chrome. Outside of the editor as it's own html file it has no problems. Just when it's in the Telerik Editor
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> </head> <body> <table width="600" cellspacing="0" cellpadding="0" border="0" align="center"> <tbody> <tr> <td> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tbody> <tr> <td> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tbody> <tr> <td valign="top"> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tbody> <tr> <td valign="top"> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tbody> <tr> <td valign="top" style="background-color: #616265;"> </td> </tr> <tr> <td> <table width="100%" cellspacing="20" cellpadding="0" border="0"> <tbody> <tr> <td> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tbody> </tbody> </table> </td> </tr> </tbody> </table> </td> </tr> <tr> <td style="background-color: #616265;"> <table width="100%" cellspacing="20" cellpadding="0" border="0"> <tbody> <tr> <td> <table width="100%" cellspacing="0" cellpadding="0" border="0"> </table> </td> </tr> </tbody> </table> </td> </tr> <tr> <td style="width: 556px; background-color: #bdbdbd;"><br /> </td> </tr> </tbody> </table> </td> </tr> </tbody> </table> </td> <td style="width: 22px; background-color: #bdbdbd;"><br /> </td> </tr> </tbody> </table> </td> </tr> </tbody> </table> </td> </tr> </tbody> </table> <br /> <br /> <br /> </body></html>3 Answers, 1 is accepted
0
Hi Chad,
An issue similar to the described scenario is already logged and I suggest following this feedback portal item and test if the provided workaround resolves the issue on your end.
Regards,
Ianko
Telerik
An issue similar to the described scenario is already logged and I suggest following this feedback portal item and test if the provided workaround resolves the issue on your end.
Regards,
Ianko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Chad
Top achievements
Rank 1
Rank 1
answered on 19 Jun 2014, 01:38 PM
As it was only suggested as a "possible" workaround can we get a little more information on why this is happening and if it's a bug that will be fixed in the future? Obviously the resize widget function was put in your code for a reason and using a workaround isn't really a solution in the long run.
0
Hello Chad,
This issue happens dye to the feature provided in the RadEditor and allows users to resize images and tables in the content area. The feature is designed to initialize a complex logic of resizable div elements in the content that upon event handlers attached to the resize handles DOM resize event triggers a logic to change dynamically the size of the selected table or image element.
Due to its complexity, when multitude of tables are nested, the initialization process causes a performance issue and it appears that there are scenarios where Chrome cannot handle to render the elements and freezes.
This matter is logged and will be further investigated by the dev team, although due to its complex matter I am unable to provide a firm estimation when exactly it is going to be properly resolved.
Do not hesitate contacting me again in case you need further information on this matter.
Regards,
Ianko
Telerik
This issue happens dye to the feature provided in the RadEditor and allows users to resize images and tables in the content area. The feature is designed to initialize a complex logic of resizable div elements in the content that upon event handlers attached to the resize handles DOM resize event triggers a logic to change dynamically the size of the selected table or image element.
Due to its complexity, when multitude of tables are nested, the initialization process causes a performance issue and it appears that there are scenarios where Chrome cannot handle to render the elements and freezes.
This matter is logged and will be further investigated by the dev team, although due to its complex matter I am unable to provide a firm estimation when exactly it is going to be properly resolved.
Do not hesitate contacting me again in case you need further information on this matter.
Regards,
Ianko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.