In rich text editor, image not initially visible when first inserted

[Maurice Stokes]

I am having an issue with the rich text editor inserting images into a content page using Chrome.  When attempting to insert an image after a header line, the image does not appear immediately, but does appear when you toggle from design to html then back to design view.  The image is there, but is between an opening and closing break tag, and isn’t visible.  Toggling between design and html view appears to clean up the html by removing the beginning break tag and turning the ending break tag into an opening break tag, which appears after the image, rendering the image visible. I have attached a screen shot of the issue.  Is there a way to control the html markup when the image is first inserted, so that the image is not between break tags? Thanks.

[Vessy]

Hi Maurice,

We are not aware of this issue and, unfortunately, the provided information was not enough to reproduce it on our side. Can you share the exact steps to replicate the issue and the Telerik version used in your application? Are you able to replicate the problem in our online demos?
http://demos.telerik.com/aspnet-ajax/editor/examples/filemanagers/defaultcs.aspx

Regards,
Vessy
Telerik by Progress

[Maurice Stokes]

Thanks for the reply Vessy.  We currently have a mature CMS that heavily uses Telerik controls.  The Telerik version we use for the CMS version that the problem exists in, is 2011.2.915.40.  The steps to reproduce the problem in our CMS is:

1.  Open the rich text editor to edit page content.

2.  Place the cursor next to some header text, press the enter key to go to the next line.

3.  Insert an image.  The image will not appear, until the html tab, then the design tab are pressed.

I could not reproduce the issue with the link you provided.  http://demos.telerik.com/aspnet-ajax/editor/examples/filemanagers/defaultcs.aspx.  Could it be the version of Telerik that is causing the issue?

[Vessy]

Hi Maurice,

Thank you for the provided additional information. The version used by you is rpetty old and the problem seems to be specific to it, indeed. We have implemented many features and improvements since 2011, furthermore the latest Chrome version was not available as of then, thus it is possible to experience issues in the modern browsers that were not released back in the time when the used by you Telerik version was.


This is why, upgrading to the latest version of the controls is the only solution I can suggest you for this moment.

Regards,
Vessy
Progress Telerik