Hi,
We have used the RadEditor for some months now, and although it works a lot better than our previous solution, I thought I'd report some issues:
1,
Multiple SPAN tags: When setting for example font size, style and color, chances are the editor will create individual SPAN tags for each css value. This works fine in most HTML viewers, of course, but there are a couple of issues with this. Firstly, the HTML becomes bloated and harder to read/change,and secondly, some HTML viewers (like certain email readers) get confused and only "see" one of the SPAN tags.
Is there any way you could make the editor reuse already existing SPAN tags? Instead of <span style="font-size: 11px"><span style="color: red;"> it would be better to have <span style="font-size: 11px; color: red;">, i.e. within the same tag.
2,
Font size is still not shown correctly at all times. Often, when selecting text, the dropdownbox for font size will show size from 1-7, instead of pixels. At other times, it will show the size in points (pt). I understand you're having problems with the way the browser handles this, but do you think there is any chance that future versions of the editor will always show correct font size or is it imposssible?
3,
As users create complex HTML documents with tables, etc, the HTML will sometimes become corrupted and contain invalid HTML like empty HTML tags (<>), end tags without start tags or tags appearing in invalid places like between TD tags for example. It would be nice to have some sort of cleaner functionality in the editor to automatically remove "garbage" HTML, or better yet, have the editor make sure such things never happen in the first place! :-) As it is, I have to help the user clean up their HTML, which means a lot of wasted time.
Regards,
Tommy Johansen
We have used the RadEditor for some months now, and although it works a lot better than our previous solution, I thought I'd report some issues:
1,
Multiple SPAN tags: When setting for example font size, style and color, chances are the editor will create individual SPAN tags for each css value. This works fine in most HTML viewers, of course, but there are a couple of issues with this. Firstly, the HTML becomes bloated and harder to read/change,and secondly, some HTML viewers (like certain email readers) get confused and only "see" one of the SPAN tags.
Is there any way you could make the editor reuse already existing SPAN tags? Instead of <span style="font-size: 11px"><span style="color: red;"> it would be better to have <span style="font-size: 11px; color: red;">, i.e. within the same tag.
2,
Font size is still not shown correctly at all times. Often, when selecting text, the dropdownbox for font size will show size from 1-7, instead of pixels. At other times, it will show the size in points (pt). I understand you're having problems with the way the browser handles this, but do you think there is any chance that future versions of the editor will always show correct font size or is it imposssible?
3,
As users create complex HTML documents with tables, etc, the HTML will sometimes become corrupted and contain invalid HTML like empty HTML tags (<>), end tags without start tags or tags appearing in invalid places like between TD tags for example. It would be nice to have some sort of cleaner functionality in the editor to automatically remove "garbage" HTML, or better yet, have the editor make sure such things never happen in the first place! :-) As it is, I have to help the user clean up their HTML, which means a lot of wasted time.
Regards,
Tommy Johansen
1 Answer, 1 is accepted
0
Hi Tommy,
Thank you for your feedback!
Up to the questions:
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thank you for your feedback!
Up to the questions:
- We are aware of the nested span tags problem and it is logged in our bug tracking system for fixing.
-
In the latest version of RadEditor for ASP.NET AJAX, the Real Font Size dropdown applies font
sizes in pixels (px). In addition to this, the client-side ConvertFontToSpan filter will convert the font tags with size attributes to span tags with style="font-size" in pixels, e.g.
<font size=1>test</font>
to
<span style="font-size: 10px">test</span>
However, please note that the Real Font Size dropdown header displays the font size value supplied by the browser as they are. It is the browser that displays the values from 1 to 7 when the font sizes in pixels correspond to these browser values. You should not worry about this because the values from 1 to 7 will be converted back to pixels when submitting the content or switching to Html mode. - When the content is submitted directly from Design mode or the user has switched from Html to Design mode and submitted the content then the content is parsed and validated by the Rich Text Editing engine of the browser used by RadEditor - the content validation is built-in in the RTF engine of the browser.
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center