HTML::Parser: report implicit events

[Bjoern Hoehrmann]

Hi,

I wonder, why HTML::Parser does not report implicit events. A conforming
parser should report them in order to insure, that a correct parse tree
could be build. An example:

  
  
  some text more textheading

should report (omitting text and possibly default events)

  declaration
  start (html)
start (head)
  start (title)
  end (title)
end (head)
start (body)
  start (p)
start (img)
end (img)
  end (p)
  start (h1)
  end (h1)
end (body)
  end (html)

I request an option to get those events.
-- 
Björn Höhrmann ^ mailto:[EMAIL PROTECTED] ^ http://www.bjoernsworld.de
am Badedeich 7 ° Telefon: +49(0)4667/981028 ° http://bjoern.hoehrmann.de
25899 Dagebüll # PGP Pub. KeyID: 0xA4357E78 # http://learn.to/quote [!]e
-- listen, learn, contribute -- David J. Marcus 

Re: HTML::Parser: report implicit events

[Gisle Aas]

Bjoern Hoehrmann <[EMAIL PROTECTED]> writes:

> I wonder, why HTML::Parser does not report implicit events. A conforming
> parser should report them in order to insure, that a correct parse tree
> could be build. An example:
> 
>   
>   
>   some text more textheading
> 
> should report (omitting text and possibly default events)
> 
>   declaration
>   start (html)
> start (head)
>   start (title)
>   end (title)
> end (head)
> start (body)
>   start (p)
> start (img)
> end (img)
>   end (p)
>   start (h1)
>   end (h1)
> end (body)
>   end (html)
> 
> I request an option to get those events.

This involves moving all the HTML::TreeBuilder logic to HTML::Parser.
I don't think I want to try to do that.  It might be possible to move
the HTML::TreeBuilder logic that insert implicit events into a
separate subclass so that it can be used without the tree generation
stuff, but then again the logic itself might need the tree to decide
what implicit tags to insert.

--Gisle