Manuel Lemos wrote:
Some people insist on making everything XHTML compliant just they assume
that otherwise it would not be "Web standards" compliant. That is a
silly claim that only leads to all sorts of problems.
That assertion is 100% untrue.
First of all, XHTML is an excellent idea. Having been based in XML
(which is easier to parse than SGML - the markup base for HTML), XHTML
is a much, much more interoperable standard. Second of all, the spec
has made a number of clarifications which should result in more
cross-browser predictability.
For instance, if you use method="post" because XHTML specification says
everything should be in lower case, you will have problems with some
browsers and e-mail programs that only accept POST in upper case and
fallback to GET when they find something else.
Oh, for God's sake, stop selling snake oil. I'm willing to bet $100
that you haven't even read the specification and are inventing crap as
you go.
For the record, the specification does not say that attribute values
need to be lowercase, only attribute *names*. You can put "PoST" or
"pOST" if you feel like it, and the markup validation status will not
change a bit.
Also, keep in mind that you can't use Javascript in HTML e-mail messages.
That's evidently true, I cannot argue with that.
These may not be your actual problems, but at least you have something
to start checking.
The original poster's problem may be related to the fact that, perhaps,
he's checking for the value of a button in the POST variable, when it's
a very well known fact that the browser only sends the value of the
button if the user *clicks* the button, but not if the user hits ENTER
in one of the form fields.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
