lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV bug printing text


From: Hiram Lester, Jr.
Subject: Re: LYNX-DEV bug printing text
Date: Wed, 26 Mar 1997 17:30:17 -0600 (CST)

On Wed, 26 Mar 1997, Laura Eaves wrote:

> I've noticed when I print a doc
> submit buttons with value strings defined are rendered as
>       ____________
> (i.e., underscores instead of the value string).
> This also happens sending a comment when lynx asks whether I
> want to include the current page in the email.  The included
> page translates submit buttons as blank lines.
> 
> I looked at the html source.  The submit button is defined as
>       <INPUT TYPE=submit VALUE="some string">
> 
> Thought I'd mention it.
> --le

Yes, this is just the way lynx works with buttons.  My understanding is
that it makes two passes on forms.  For the first pass, it leaves ___ as a
placeholder for the VALUE attribute to be filled in on the second pass.
My understanding is that in order to get it to do it in a more sensible
manner, the form handling code would basically have to be written from the
ground up.

   +------------------------------------+-------------------------------+
   | Hiram W. Lester, Jr..               | E-Mail: address@hidden    |
   | Computer Science                   | Home page:                    |
   | Middle Tennessee State University  |   http://pobox.com/~hwlester/ |
   +------------------------------------+-------------------------------+

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]