We use the RadEditor in our web application to allow non-technical users create/edit simple HTML content using the Design view. However, it seems the HTML generated by the design view is buggy or inconsistent causing numerous complaints from our end users. I am wondering if there are any properties or filters that could be applied to make the end user experience more predictable.
Normally we are very happy with all Telerik AJAX
controls. Therefore we have switched recently from CuteSoft editor to
RadEditor. However, the experience with RadEditor has been very bad, to the point we have received numerous requests from our users to switch back to CuteSoft control to make the system
more stable again.
Here is an example:
Using the Design View create a bulleted list (basically UL LI construct) containing 3 bullets: Link1, Link2, Link3. Using the designer, set the Link1, Link2 and Link3 to the following URLs “http://link1.com”, “http://link2.com”, “http://link3.com”.
This will create the following HTML syntax. So far so good...
<li><a href="http://link1.com">Link 1</a></li>
<li><a href="http://link2.com">Link 2</a></li>
<li><a href="http://link3.com">Link 3</a></li>
Then using the Design view, highlight the entire text and change color to RED.
For whatever reason, the span construct is applied differently to each LI. In some cases it is added outside of the Anchor element, in other cases it is included inside of the Anchor element. It produces the following output (see how link1 anchor is different from link2 anchor) - although we tried more than once and sometimes 2 out of 3 LI elements have correct format....
<li><a href="http://link1.com"><span style="color: #c00000;">Link 1</span></a></li>
<li><span style="color: #c00000;"><a href="http://link2.com">Link 2</a></span></li>
<li><span style="color: #c00000;"><a href="http://link3.com">Link 3</a></span></li>
In that situation, in the DESIGN view, it is impossible to change the color of link2 or 3 since the span color is outside of the Anchor element. Note: I was able to reproduce the same exact behavior on your demo site http://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx in both Chrome and IE11.
Again, non-technical users don't understand this problem. The steps they follow seem logical, yet the output is inconsistent. There are many other cases like this one, so the problem is not specific to UL LI and Anchor syntax.
Please advise on a possible solution.