Re: Going from simple to super CAPTCHA
| From: | Robin Vickery | Date: | Thu, 14 Jun 2007 08:23:28 +0000 |
| Subject: | Re: Going from simple to super CAPTCHA | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-256971@lists.php.net to get a copy of this message | ||
On 13/06/07, Richard Lynch <ceo@l-i-e.com> wrote:
On Wed, June 13, 2007 3:36 am, Robin Vickery wrote: On 12/06/07, Richard Lynch <ceo@l-i-e.com> wrote:Well, it'd be pretty safe to require HTML 2.0 or higher. From the HTML 2.0 Spec [RFC-1866] 8.2.1 part 2 "The fields are listed in the order they appear in the document with the name separated from the value by `=' and the pairs separated from each other by `&'. Fields with null values may be omitted." -robinThe HTML spec says that form elements should be presented in the order they appear in the document. If the browser doesn't conform to spec, it's not his fault. From the HTML 4.01 Specification: "The control names/values are listed in the order they appear in the document. The name is separated from the value by `=' and name/value pairs are separated from each other by `&'." Cool! I wonder if that came about as a result of HTML 3.x "issues"... :-) Might be where I remembered the ordering issue from. I guess it's okay to require HTML 4.01 or higher now, eh?...On Tue, June 12, 2007 9:33 am, Tijnema wrote:I meant reverse order :PThat would be pretty broken. There's no guarantee that browsers will present the inputs in any order at all, even though they all seem (so far) to follow the convention of presenting them in the order they appear in the form. If, however, one browser decides tomorrow to use the "tab" order instead, and your code breaks because of that, it's your fault, not the browser's.