HTML::Form(3pm) | User Contributed Perl Documentation | HTML::Form(3pm) |
HTML::Form - Class that represents an HTML form element
version 6.11
use HTML::Form; $form = HTML::Form->parse($html, $base_uri); $form->value(query => "Perl"); use LWP::UserAgent; $ua = LWP::UserAgent->new; $response = $ua->request($form->click);
Objects of the "HTML::Form" class represents a single HTML "<form> ... </form>" instance. A form consists of a sequence of inputs that usually have names, and which can take on various values. The state of a form can be tweaked and it can then be asked to provide HTTP::Request objects that can be passed to the request() method of LWP::UserAgent.
The following methods are available:
The required arguments is the HTML document to parse ($html_document) and the URI used to retrieve the document ($base_uri). The base URI is needed to resolve relative action URIs. The provided HTML document should be a Unicode string (or US-ASCII).
By default HTML::Form assumes that the original document was UTF-8 encoded and thus encode forms that don't specify an explicit accept-charset as UTF-8. The charset assumed can be overridden by providing the "charset" option to parse(). It's a good idea to be explicit about this parameter as well, thus the recommended simplest invocation becomes:
my @forms = HTML::Form->parse( Encode::decode($encoding, $html_document_bytes), base => $base_uri, charset => $encoding, );
If the document was retrieved with LWP then the response object provide methods to obtain a proper value for "base" and "charset":
my $ua = LWP::UserAgent->new; my $response = $ua->get("http://www.example.com/form.html"); my @forms = HTML::Form->parse($response->decoded_content, base => $response->base, charset => $response->content_charset, );
In fact, the parse() method can parse from an HTTP::Response object directly, so the example above can be more conveniently written as:
my $ua = LWP::UserAgent->new; my $response = $ua->get("http://www.example.com/form.html"); my @forms = HTML::Form->parse($response);
Note that any object that implements a decoded_content(), base() and content_charset() method with similar behaviour as HTTP::Response will do.
Additional options might be passed in to control how the parse method behaves. The following are all the options currently recognized:
Example:
push_input( 'hidden', { name => 'NewFormElement', id => 'NewFormElementId', value => 'some value', });
Example:
@f = HTML::Form->parse( $html, $foo ); @f = grep $_->attr("id") eq "foo", @f; die "No form named 'foo' found" unless @f; $foo = shift @f;
If $selector is not "undef", then the input's name, id or class attribute must match. A selector prefixed with '#' must match the id attribute of the input. A selector prefixed with '.' matches the class attribute. A selector prefixed with '^' or with no prefix matches the name attribute.
my @by_id = $form->find_input( '#some-id' ); my @by_class = $form->find_input( '.some-class' ); my @by_name = $form->find_input( '^some-name' ); my @also_by_name = $form->find_input( 'some-name' );
If you want to find an input that has no name at all, pass in a reference to "undef".
my @nameless_inputs = $form->find_input( \undef );
If $type is not "undef", then the input must have the specified type. The following type names are used: "text", "password", "hidden", "textarea", "file", "image", "submit", "radio", "checkbox" and "option".
The $index is the sequence number of the input matched where 1 is the first. If combined with $selector and/or $type, then it selects the nth input with the given name and/or type.
If multiple inputs have the same name, only the first one will be affected.
The call:
$form->value('foo')
is basically a short-hand for:
$form->find_input('foo')->value;
If called without arguments then it returns the names of all the inputs in the form. The names will not repeat even if multiple inputs have the same name. In scalar context the number of different names is returned.
If called with a single argument then it returns the value or values of inputs with the given name. If called in scalar context only the first value is returned. If no input exists with the given name, then "undef" is returned.
If called with 2 or more arguments then it will set values of the named inputs. This form will croak if no inputs have the given name or if any of the values provided does not fit. Values can also be provided as a reference to an array. This form will allow unsetting all values with the given name as well.
This interface resembles that of the param() function of the CGI module.
If a $selector is specified, we will click on the first clickable input matching the selector, and the method will croak if no matching clickable input is found. If $selector is not specified, then it is ok if the form contains no clickable inputs. In this case the click() method returns the same request as the make_request() method would do. See description of the find_input() method above for how the $selector is specified.
If there are multiple clickable inputs with the same name, then there is no way to get the click() method of the "HTML::Form" to click on any but the first. If you need this you would have to locate the input with find_input() and invoke the click() method on the given input yourself.
A click coordinate pair can also be provided, but this only makes a difference if you clicked on an image. The default coordinate is (1,1). The upper-left corner of the image is (0,0), but some badly coded CGI scripts are known to not recognize this. Therefore (1,1) was selected as a safer default.
In scalar context this method returns the number of key/value pairs generated.
HTML::Form - Class that represents an HTML form element
An "HTML::Form" object contains a sequence of inputs. References to the inputs can be obtained with the $form->inputs or $form->find_input methods.
Note that there is not a one-to-one correspondence between input objects and <input> elements in the HTML document. An input object basically represents a name/value pair, so when multiple HTML elements contribute to the same name/value pair in the submitted form they are combined.
The input elements that are mapped one-to-one are "text", "textarea", "password", "hidden", "file", "image", "submit" and "checkbox". For the "radio" and "option" inputs the story is not as simple: All <input type="radio"> elements with the same name will contribute to the same input radio object. The number of radio input objects will be the same as the number of distinct names used for the <input type="radio"> elements. For a <select> element without the "multiple" attribute there will be one input object of type of "option". For a <select multiple> element there will be one input object for each contained <option> element. Each one of these option objects will have the same name.
The following methods are available for the input objects:
If strict is enabled and the input only can take an enumerated list of values, then it is an error to try to set it to something else and the method will croak if you try.
You will also be able to set the value of read-only inputs, but a warning will be generated if running under "perl -w".
When setting values using the value() method it is also possible to use the value names in place of the value itself.
This has the same effect as:
$input->value($input->possible_values[1]);
The input can be turned off with:
$input->value(undef);
If the input is of type "file", then it has these additional methods:
For security reasons this field will never be initialized from the parsing of a form. This prevents the server from triggering stealth uploads of arbitrary files from the client machine.
LWP, LWP::UserAgent, HTML::Parser
Gisle Aas <gisle@activestate.com>
This software is copyright (c) 1998 by Gisle Aas.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
2023-02-14 | perl v5.36.0 |