If that is not valid html, should it not raise an error instead of returning an incorrect parse tree?

Is there any way of making it parse it the way it is written anyway?

Chris

Am 08.06.2014 17:16 schrieb "Ben Hyde" <bhyde@pobox.com>:
Ah, the joys of HTML - see, for example: http://stackoverflow.com/questions/9852312/list-of-html5-elements-that-can-be-nested-inside-p-element

On Jun 8, 2014, at 9:47 AM, Christopher Laux <ctlaux@gmail.com> wrote:
Hi,

I think I've found a bug in closure. If I execute

(chtml:parse "<small><p>test1</p><p>test2</p></small>" (chtml:make-lhtml-builder))

> (:HTML NIL (:HEAD NIL)
 (:BODY NIL (:SMALL NIL) (:P NIL (:SMALL NIL "test1")) (:P NIL "test2")))

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).

Any help?

Chris

_______________________________________________
Closure-devel mailing list
Closure-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/closure-devel