line break tags get broken

6 replies. Last post: June 19, 2011 10:25 PM by Yudi
Tags :
  • (None)
  • New Discussion
  • New Question
  • New Product Feedback

Version: 1.0.1000.33 (the hotfix you sent us in a previous thread).  Also observed with .23.

Steps to reproduce:

  • given a WebTextEditor with no text in it, switch to "HTML" mode.
  • Enter a line break tag - you can use "<br>" or "<br/>"
  • Switch to "Design" mode.
  • Switch back to "HTML" mode.
Expected: Best case, should see the same HTML that was entered.  Worst case, at least something equivalent.
Actual: The "<br>" or "<br/>" tag is replaced with "<br></br>".  This it not valid HTML, and in browsers it gets rendered as two line breaks.
More: If you switch back and forth between "Design" and "HTML" some more, the number of line breaks will double every time.
We've also noticed that the tool inserts a "<tbody>" element into tables, and we're pretty sure it makes other changes as well.  Is there any way to run the WebTextEditor so that it just doesn't change the HTML that you type in?
Thanks for your help!

Oh and one other point, the browser is running in "IE9 Standards" document mode, in case that helps.

Yudi Member

The information about browser version really helps to reproduce the issue on my local end.

I have submitted this issue to WebTextEditor development team as work item #1020. I will let you know any news I heard from the team regarding work item #1020.

I also would like to add something that I found during my attempt to reproduce the issue. The issue is not persisting when IE 9 is open in quirk mode. As a workaround, you might try to add following line into the <head> tag of your page in order to have the page open in quirk mode (by default).

<meta http-equiv="X-UA-Compatible" content="IE=5" />

Hi Yudi,

Unfortunately we recently finished a big project to take our web application out of quirks mode, so your workaround is not a good option for us.  Thanks for submitting our issue, we will stand by for an update.

Yudi Member

Thank you for the prompt reply.

I just checked the status of work item #1020 and found that it hasn’t been solved yet. I’ll let you know when the pre-release hotfix is ready to be tested.

All times are GMT -5. The time now is 10:36 AM.
Previous Next