"David Dorward" <dorward@[EMAIL PROTECTED]
> wrote in message
news:dhrr87$4q$1$8300dec7@[EMAIL PROTECTED]
> >
> > Well, I found part of the problem. It's actually IE that returns
innerText
> > rather than the <button>'s value, contrary to the W3C recommendations.
>
> Yes, IE is very broken.
>
> > So now it's onward to <input type="image">.
>
> Most browsers don't send the value of image types, just the coordinates
that
> were clicked.
>
> > Are there any limitations on what characters make up "name"?
>
> Not that I'm aware of, but its probably best to stick to alphanumerics
and
> underscores.
According to W3C (not that Microsoft seems to care) the "name" is case
insensitive CDATA which tends to indicate anything goes ... except for
leading/trailing white space, carriage returns, and the like. But to get
around my problem (thanks to yet another ancient bug in IE) all the names
will have to be unique and, since the row associated with the <input
type="image> buttons represents a row from a database, the button names
will
have to be a combination of the action (edit/delete) and the key value.
The
key value will certainly be more than just alphanumeric information. All
the
real work is being done with server-side classic VBScript in ASP pages
(fun,
fun, fun) so I'm trying to also figure out a way to encode/decode these
strings to keep from throwing inadvertent HTML into the mix.
|
