Quantcast
Channel: AjaxControlToolkit Work Item Rss Feed
Viewing all articles
Browse latest Browse all 4356

Commented Issue: Issues in HTMLEditor Extender in May 2012 Release [27154]

$
0
0
Hi,

I found some issues in New HTML Editor Extendor. It has different behaviour in Mozila & internet Explorer.

In internet explorer after typing First line in editor, if I press the Enter, then my first line going down to second. This is due to the <p> tag generated in place of <br /> by HTMLEditor Extender.

For BOLd: In internet explorer, it generate <strong> tag while in Mozila, it generate <b> tag.

New Line: New line generate <p> tag in Internet exporer & <br> in Mozila (it should be <br />).

In Mozila, in postpack it doesn't preserve its formatting & doesn't send formatted Text to server side code while in case of internet explorer, it works.

Font Background color is not also working properly.

Also there are other several issues in this release of AjaxcontrolToolkit.


Comments: Hello, Each browser generates different HTML . Under the hood, the HtmlEditorExtender uses the HTML5 ContentEditable attribute to create a rich text editor. ContentEditable is implemented in different ways in the case of different browsers. For example, if you click the bold button in the HtmlEditorExtender using IE then you get <STRONG> strong tags. If you use Chrome then you get <b> B tags. Again, it is really up to the browser. We have been investigating using Regular Expressions to translate into canonical tags. For example, always replacing <strong> strong tags with <b> B tags. I've added a feature request for this at http://ajaxcontroltoolkit.codeplex.com/workitem/27159 If you want this feature then please vote for it. I was able to reproduce the background color issue that you report with Firefox. I've created a separate issue for this at: http://ajaxcontroltoolkit.codeplex.com/workitem/27158 -- Stephen

Viewing all articles
Browse latest Browse all 4356

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>