We have had several users with this problem, but I am unable to replicate it on my system. Near as I can tell, they edit a page, typing in text, save the page, and what is saved is not only the text they have typed but also many <br> tags both between the text that they've typed and after it. Usually there are 5-21 lines of <br>s between text, but some of them have hundreds of <br>s after the text. This is rendering our tool unusable. We are currently using <!-- 2010.1.519.20 -->. We thought initially that they were pasting from Word, but that is not the case. We are trying to track users down and gather further information from them, and I'll report back any clarifying info I receive. Initial reports indicate it may be an IE issue and not a FF issue. Any ideas people may have off the tops of your heads would be helpful.
Thanks!
Laurie
Thanks!
Laurie
8 Answers, 1 is accepted
0
Hi Laurie,
You can experience such a problem in version 2010.1.519.20 under IE9. We provided support for IE9 in Q1 2011 (v2011.1.315). My recommendation is to upgrade to the latest official release Q1 2011 SP2 where this IE9 problem is fixed.
In the meantime as a workaround you can disable the ConvertToXhtml filter and the problem should disappear.
Best regards,
Rumen
the Telerik team
You can experience such a problem in version 2010.1.519.20 under IE9. We provided support for IE9 in Q1 2011 (v2011.1.315). My recommendation is to upgrade to the latest official release Q1 2011 SP2 where this IE9 problem is fixed.
In the meantime as a workaround you can disable the ConvertToXhtml filter and the problem should disappear.
Best regards,
Rumen
the Telerik team
Browse the vast support resources we have to jump start your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
0
Laurie
Top achievements
Rank 2
answered on 20 Jun 2011, 05:31 PM
I am running under .NET 2.0 so can't run v2011.1.315. The last version I can run is <!-- 2010.3.1317.20 -->. Does this version also fix the IE9 issue?
0
Hi Laurie,
Please see this blog post which explains why we do not ship .NET 2 assemblies of our AJAX controls starting Q1 2011. Yes, you can use the old Q3 2010 SP2 to develop under .NET 2 framework, but it does not offer support for IE9 and you will experience the <br/> problem, except:
All the best,
Rumen
the Telerik team
Please see this blog post which explains why we do not ship .NET 2 assemblies of our AJAX controls starting Q1 2011. Yes, you can use the old Q3 2010 SP2 to develop under .NET 2 framework, but it does not offer support for IE9 and you will experience the <br/> problem, except:
- you do not disable the ConvertToXhtml filter
RadEditor1.DisableFilter(Telerik.Web.UI.EditorFilters.ConvertToXhtml);
- or render the page in IE8 mode using the meta tag below:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
All the best,
Rumen
the Telerik team
Browse the vast support resources we have to jump start your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
0
Laurie
Top achievements
Rank 2
answered on 21 Jun 2011, 04:16 PM
I'm not quite following what you're saying. Do you mean that I should or should not disable the convertoxhtml filter or that I shoudl or should not include the IE8 mode meta tag in order to get around this issue?
0
Accepted
Rumen Jekov
Top achievements
Rank 1
answered on 21 Jun 2011, 07:56 PM
Hi,
The problem exists in IE9 only and is reproducible when the ConvertToXhtml filter is enabled.
What you can do is to:
- disable the ConvertToXhtml filter - which of course is not recommended, because the content will be not validated and non XHTML compliant
OR
- keep the ConvertToXhtml filter enabled, but render the page in IE8 mode in IE9 using the meta tag:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
Another approach is to run your project under .NET 3.5 or 4.0 and upgrade the editor to the latest build Q1 2011 SP2 where the problem is fixed.
Let me know if you need additional instructions.
Regards,
Rumen
The problem exists in IE9 only and is reproducible when the ConvertToXhtml filter is enabled.
What you can do is to:
- disable the ConvertToXhtml filter - which of course is not recommended, because the content will be not validated and non XHTML compliant
OR
- keep the ConvertToXhtml filter enabled, but render the page in IE8 mode in IE9 using the meta tag:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
Another approach is to run your project under .NET 3.5 or 4.0 and upgrade the editor to the latest build Q1 2011 SP2 where the problem is fixed.
Let me know if you need additional instructions.
Regards,
Rumen
0
Laurie
Top achievements
Rank 2
answered on 21 Jun 2011, 08:20 PM
Thanks, that's much clearer. The meta-tag fix appears to work. Switching over from 2.0 to 3.5 at this point is not practical for us.
Laurie
Laurie
0
Juliano Araujo
Top achievements
Rank 1
answered on 23 Mar 2012, 02:23 PM
Is this problem has been sorted? It doesn't seems to work on mine.
Thanks
Thanks
0
Laurie
Top achievements
Rank 2
answered on 23 Mar 2012, 03:20 PM
We have not experienced the issue since I added the meta tag.