
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Ah, the joys of HTML - see, for example: <a href="http://stackoverflow.com/questions/9852312/list-of-html5-elements-that-can-be-nested-inside-p-element">http://stackoverflow.com/questions/9852312/list-of-html5-elements-that-can-be-nested-inside-p-element</a></div><br><div><div>On Jun 8, 2014, at 9:47 AM, Christopher Laux <<a href="mailto:ctlaux@gmail.com">ctlaux@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div>I think I've found a bug in closure. If I execute</div><div><br></div><div>(chtml:parse "<small><p>test1</p><p>test2</p></small>" (chtml:make-lhtml-builder))<br>

</div><div><br></div><div>> (:HTML NIL (:HEAD NIL)</div><div> (:BODY NIL (:SMALL NIL) (:P NIL (:SMALL NIL "test1")) (:P NIL "test2")))</div><div><br></div><div>I get that incorrect parse tree. The example is taken from a real website and the same happens inside the entire page. That happens both with the current git version and the quicklisp version (which might just be the same one).</div>

<div><br></div><div>Any help?</div><div><br></div><div>Chris</div><div><br></div></div>

_______________________________________________<br>Closure-devel mailing list<br><a href="mailto:Closure-devel@common-lisp.net">Closure-devel@common-lisp.net</a><br>http://common-lisp.net/cgi-bin/mailman/listinfo/closure-devel<br></blockquote></div><br></body></html>