fillinform(source, form_data)

    my $fillinform = fillinform($query);
    $fillinform->($html); # the same as fillinform($html, $query)

This function is exportable.

new(options...)

There are several options. All the options are disabled when "undef" is supplied.

Acceptable options are as follows:

fill_password => bool

To enable passwords to be filled in, set the option true.

Note that the effect of the option is the same as that of "HTML::FillInForm", but by default "HTML::FillInForm::Lite" ignores password fields.

ignore_fields => array_ref_of_fields

To ignore some fields from filling.

target => form_id

To fill in just the form identified by form_id.

escape => bool | ref

If true is provided (or by default), values filled in text fields will be HTML-escaped, e.g. "<tag>" to be "&lt;tag&gt;".

If the values are already HTML-escaped, set the option false.

You can supply a subroutine reference to escape the values.

Note that it is not implemented in "HTML::FillInForm".

decode_entity => bool | ref

If true is provided , HTML entities in state fields (namely, "radio", "checkbox" and "select") will be decoded, but normally it is not needed.

You can also supply a subroutine reference to decode HTML entities.

Note that "HTML::FillInForm" always decodes HTML entities in state fields, but not supports this option.

layer => :iolayer

To read a file with :iolayer. It is used when a file name is supplied as source.

For example:

    # To read a file encoded in UTF-8
    $fif = HTML::FillInForm::Lite->new(layer => ':utf8');
    $output = $fif->fill($utf8_file, $fdat);

    # To read a file encoded in EUC-JP
    $fif = HTML::FillInForm::Lite->new(layer => ':encoding(euc-jp)');
    $output = $fif->fill($eucjp_file, $fdat);
    

Note that it is not implemented in "HTML::FillInForm".

fill(source, form_data [, options...])

options are the same as "new()"'s.

You can use this method as a both class or instance method, but you make multiple calls to "fill()" with the same options, it is a little faster to call "new()" and store the instance.

source may be a scalar reference, an array reference of strings, or a file name.

form_data may be a hash reference, an object with "param()" method, an object with accessors, a code reference, or an array reference of those above mentioned.

If form_data is based on procedures (i.e. not a hash reference), the procedures will be called in the list context. Therefore, to leave some fields untouched, it must return a null list "()", not "undef".

Compatibility with "HTML::FillInForm"

Compatibility with legacy HTML

And it also supporting a good part of HTML 4.x , but there are some limitations. First, it doesn't understand HTML-attributes that the name is omitted.

For example:

    <INPUT TYPE=checkbox NAME=foo CHECKED> -- NG.
    <INPUT TYPE=checkbox NAME=foo CHECKED=checked> - OK, but obsolete.
    <input type="checkbox" name="foo" checked="checked" /> - OK, valid XHTML

Then, it always treats the values of attributes case-sensitively. In the example above, the value of "type" must be lower-case.

Moreover, it doesn't recognize omitted closing tags, like:

    <select name="foo">
        <option>bar
        <option>baz
    </select>

When you can't get what you want, try to give your source to a HTML lint.

Comment handling

It may cause problems. Suppose there is a code like:

    <script> document.write("<input name='foo' />") </script>

"HTML::FillInForm::Lite" will break the code:

    <script> document.write("<input name='foo' value="bar" />") </script>

To avoid such problems, you can use the "ignore_fields" option.