[Top][All Lists]

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

Re: lynx-dev two Forms queries

From: David Woolley
Subject: Re: lynx-dev two Forms queries
Date: Sun, 25 Jun 2000 11:26:59 +0100 (BST)

> (1) there is a link of  type="button"  with an  onclick= :

input type=button is a pure scripting element; it doesn't even have
to be on a form, although Netscape requires this.

> is it possible for the site manager to provide an  ALT  for this?

input type=button is text, so alt is irrelevant.  In an ideal world,
this element would not be used unless the aspect of the application
that it implements fundamentally requires client side scripting.

If the button actually submits the form, they should have used 
input type=submit, and, in the unlikely event that they cared about
accessibility or security issues, should have coded it as

<input type="submit" name="xxx" value="yyy"
  onclick="javascript code; return false">

However, in that case, it is unlikely that the actions are specific to that
button, so they would be better off using onsubmit on the form, and 
returning false, to abort the submission, if the validation failed.

> he denies it can be done within HTML: can anyone offer advice?

That depends on what "it" is.

> i can dodge round it by extracting the URL from the source,
> but it would be nice to be able to tell him how to make it Lynx-friendly.
> (2) on entering  \  to get both source/rendered,
> i am asked `Resubmit POST content to Application Framework? Y/N'
> why would Lynx do this?  answering `y' seems to have no bad effect.

Because POST is not required, or particularly expected, to be idempotent,
so a second POST to request $100,000 of dodgy mining stock could increase
your losses to $200,000.  (Well designed sites will use something like a
transaction serial number to detect a duplicate, but the protocol doesn't
require this.

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

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