| Subject: | -no_sticky documentation issues |
| Date: | Wed, 11 Feb 2009 16:13:52 -0900 |
| To: | bug-CGI.pm [...] rt.cpan.org |
| From: | "Britton Kerin" <bkerin [...] fastmail.fm> |
Hi,
As bug 38061 -nosticky doesn't seem to work exaclty as documented.
There is also asl this dangling reference to a -no_sticky pragma
in section FORM ELEMENTS:
A boolean, which, if true, forces the element to take on the value
specified by -value, overriding the sticky behavior described earlier
for the -no_sticky pragma.
-no_sticky (with an underscore) doesn't seem to be mentioned anywhere
else.
Another curious thing is that when I try to call $CGI::nosticky(1) as
the comments in CGI.pm suggest, I seem to always get a syntax error
at the call site, even when there isn't anything else on the line
except a semicolon.
Britton
On Tue, 10 Feb 2009 09:51:52 -0900, "Britton Kerin" <bkerin@fastmail.fm>
said:
Show quoted text
> Same as last message (just with a subject since I often don't look at
> the
> ones that don't have a subject myself):
>
> The CGI man page section CREATING A JAVASCRIPT BUTTON contains this:
>
> button() produces a button that is compatible with Netscape 2.0's
> JavaScript. When it's pressed the fragment of JavaScript code pointed to
> by the -onClick parameter will be executed. On non-Netscape browsers
> this form element will probably not even display.
>
> which I think is unduly pessimistic now. No reason for a lovely module
> like CGI.pm
> to look out of date!
>
> Britton
>
>