A question about HTML::TreeBuilder.  I am trying to use this module
in a HTML rewriting proxy.  The documentation says

BUGS
     * Currently, it's assumed that "HTML" is the top node in the
     tree, and that "HEAD" and "BODY" must be right under "HTML".
     Framesets are therefore coerced into being under "BODY",
     even if the document in question has the "BODY" inside a
     "NOFRAMES" element. This may change in a future version,

Does anything outside HTML::TreeBuilder and/or HTML::Element
depend on this assumption?

     particularly if anyone points out a case where this is
     troublesome for them.

Obviously, for a proxy, this is a major problem:
all framed pages turn out empty,

I haven't looked at the code yet; is this coercion invertible?

How easy would it be to change HTML::TreeBuilder to preserve
the structure of framed pages?

-- 
Reinier Post                                    [EMAIL PROTECTED]

Reply via email to