Empty paragraphs (<p /> ) not shown in wysiwyg (IE)

[niko]

insert a empty paragraph, switch into html-view and back and the empty paragraph won't be shown anymore, although its still in the html-code.

<p>asdf</p>
<p />
<p>asdf</p>

it is caused by the <p /> (<p /> is not visible - even on a test-html-page!)

i think this is caused by getHTMLWrapper, i did some debugging in there. as some kind of a workaround this works for me:

--- htmlarea.js (Revision 223)
+++ htmlarea.js (Arbeitskopie)
@@ -4665,7 +4665,14 @@
         html += " " + name + '="' + HTMLArea.htmlEncode(value) + '"';
       }
       if (html != "") {
-        html += closed ? " />" : ">";
+        if(closed && root_tag=="p") {
+          //never use <p /> as empty paragraphs won't be visible
+          html += ">&nbsp;</p>";
+        } else if(closed) {
+          html += " />";
+        } else {
+          html += ">";
+        }
       }
     }
     var containsBlock = false;

although it doesn't solve the real problem.

please review this patch, and report if you have the same problems too.

[wymsy]

A simpler solution might be (haven't tested on this case) to add <p> tags to the list HTMLArea._closingTags, along with h1 - h6 tags, which also have a variety of problems in IE if not closed. But I think an even better solution may lie in the approach in ticket #253, which would replace most of the getHTMLWrapper code with a set of regular expressions that clean up the innerHTML produced by the browser. This would get rid of all the hacks that have been added to getHTMLWrapper for all the special cases that keep popping up. I have been experimenting with this and it looks very promising. It seems to handle this issue, for example, as well as the special cases added for form elements (value and onclick attributes). I plan to post my test code in the next day or so under ticket #253 so others can try to break it.

[niko]

nice, i hope this will be the final solution for all of those problems...

and much faster too i think...

[niko]

commited this patch in changeset:226 to fix the bug for now, will be replaced by #253 hopefully soon

[wymsy]

Unfortunately, further testing has revealed a problem in IE that may make #253 unusable. I'll post the details under that ticket.