RadEditor allows the copy and paste of images directly into the Editor content area. The Editor converts this images to a base 64 string and includes them in the HTML. What would really be great is if it could instead convert the image to a file, perhaps even from the base 64 string, and save it server side, and instead add an img tag referencing the saved file. This would be very useful for when the editor is being used for sending emails (less space) and even creating content as the file would be able to be cached. It's already being done in the TeamPulse product when a screenshot or other image is pasted into the editor. Please extend this functionality to be built into the AJAX version.
Currently, by using ExternalDialogsPath property, developers can extend the built-in dialogs by adding the user controls in a local folder. It would be a nice-to-have feature, if these user controls can be also located in a virtual folder.
these pages shows the accessibility standards for tables.
For these two sub links "Tables with two headers" & "Tables with irregular headers", they are looking for "scope=col", "scope=row", "scope=colgroup", "scope=rowgroup".
There doesn't seem to be any built in support for "scope" to be added when using the table wizard, having set on the Accessibility tab a Heading for both a Row & Column.
Add support for "scope" be added to tables created in the Rich Text Editor.
It becomes the operation of Chrome only. after the new line, if you type continuously double-byte character string "あい",the input result was "い". The correct answer is "あい". For operation that does not occur in earlier versions, I think I've considered this release version of the bug, the cause can be identified?
The Text property of the editor converts the html into plain text. Very handy. It would be really helpful if this could be exposed as a static method on the editor for use elsewhere, without having to create an editor object. I know that I could just grab the source code and create my own, but then I don't get the benefit of improvements and bug fixes you may add in the future.
It will be possible to use Lightweight render mode with AccessibleRadEditor.