I'm using the HtmlEditorExtender control on an ASP.NET 4.0 website. In IE, Safari and Firefox the control works fine. But with Chrome and Opera the page generates this error:
```
Exception type: HttpRequestValidationException
Exception message: A potentially dangerous Request.Form value was detected from the client (ctl00$Body$MetricComment="<br>").
```
This error happens if there is __ANY__ html at all, but not on the initial form submission. It only happens when you go back to the same page and then resubmit the form with the HTML in it.
It did not fix the issue when enabling the HtmlAgilityPack sanitizer as shown on this page: http://stephenwalther.com/archive/2012/06/25/announcing-the-june-2012-release-of-the-ajax-control-toolkit
I'm also getting the following javascript error in Chrome, but I'm unsure if it is related:
```
Uncaught IndexSizeError: Failed to execute 'collapse' on 'Selection': There is no child at offset 3.
```
I tried adding the Text= " " fix found in another issue posting (https://ajaxcontroltoolkit.codeplex.com/workitem/27717) but that didn't stop the javascript error or the validation error. According to the blog post by the guys at Kartris (http://www.kartris.com/Knowledgebase/Chrome-AJAX-postback-issues-July-2014__k-56.aspx) this issue should be fixed again with Chrome 38. I'm using Chrome 38 and I'm still seeing this error. But maybe it is a different issue because I'm not seeing exactly what that issue described.
Interestingly when I switched from this control to a jQuery powered html editor the error began appearing on all browsers. This leads me to believe it is a Chrome/Opera bug with the way they are handling the HtmlEditorExtender control. However, I have my doubts that I will get anywhere quickly by posting a bug to them, especially since I'm not sure exactly what is different that is causing the issue.
I was wondering you guys knew of any workarounds for this issue? Even a good description of exactly what is going wrong could help me figure out something that might work.
Currently the only way I've gotten it to work with Chrome is to set RequestValidation="false" for the page but, of course, that is not ideal.
```
Exception type: HttpRequestValidationException
Exception message: A potentially dangerous Request.Form value was detected from the client (ctl00$Body$MetricComment="<br>").
```
This error happens if there is __ANY__ html at all, but not on the initial form submission. It only happens when you go back to the same page and then resubmit the form with the HTML in it.
It did not fix the issue when enabling the HtmlAgilityPack sanitizer as shown on this page: http://stephenwalther.com/archive/2012/06/25/announcing-the-june-2012-release-of-the-ajax-control-toolkit
I'm also getting the following javascript error in Chrome, but I'm unsure if it is related:
```
Uncaught IndexSizeError: Failed to execute 'collapse' on 'Selection': There is no child at offset 3.
```
I tried adding the Text= " " fix found in another issue posting (https://ajaxcontroltoolkit.codeplex.com/workitem/27717) but that didn't stop the javascript error or the validation error. According to the blog post by the guys at Kartris (http://www.kartris.com/Knowledgebase/Chrome-AJAX-postback-issues-July-2014__k-56.aspx) this issue should be fixed again with Chrome 38. I'm using Chrome 38 and I'm still seeing this error. But maybe it is a different issue because I'm not seeing exactly what that issue described.
Interestingly when I switched from this control to a jQuery powered html editor the error began appearing on all browsers. This leads me to believe it is a Chrome/Opera bug with the way they are handling the HtmlEditorExtender control. However, I have my doubts that I will get anywhere quickly by posting a bug to them, especially since I'm not sure exactly what is different that is causing the issue.
I was wondering you guys knew of any workarounds for this issue? Even a good description of exactly what is going wrong could help me figure out something that might work.
Currently the only way I've gotten it to work with Chrome is to set RequestValidation="false" for the page but, of course, that is not ideal.