I repeat my bug report:
Not all templating systems are string-oriented. HTML::Seamstress is not. It works with HTML::Element instances. As such, it would be nice if the result of filling in the form could be returned as a tree for further processing by HTML::Element methods. As it stands, I am forced to parse the results of HTML::FillInForm back into a tree (even though it was a tree before HTML::FillInForm stringified it).
Now, just consider how much is being done.
  1. seamstress has an HTML tree that it wants the form filled in on
  2. seamstress converts this to a string
  3. FillInForm parses the string into an HTML tree and then fills in the form
  4. FillInForm converts the HTML tree to a string
  5. seamstress re-parses the HTML for additional processing
If FillInForm could receive and return trees, my apps would be much faster.

For the time being, I at least need to turn this multiline process into a single function call, so here it is.

Of course, 

# https://rt.cpan.org/Ticket/Display.html?id=44105
sub tree_fillinform {

    my ($tree, $hashref)=@_;
    
    my $html = $tree->as_HTML;
    my $new_html = HTML::FillInForm->fill(\$html, $hashref);
    HTML::TreeBuilder->new_from_content($new_html);

}

[download]

In reply to tree-oriented use of HTML::FillInForm by metaperl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.