Now, ain't that weird - the w3c validator was giving me the hell for the name attrib, now it doesn't. Maybe it was because the name was weird. I even googled "xhtml name attribute" and found this w3c page: http://www.w3schools.com/Xhtml/xhtml_syntax.asp "The id Attribute Replaces The name Attribute HTML 4.01 defines a name attribute for the elements a, applet, frame, iframe, img, and map. In XHTML the name attribute is deprecated. Use id instead." But it doesn't says anything about the input tag, in effect. Also, I'm no more having my post variables, so I'm definitely douing something wrong - better put the names back ;)
On 5 Mar, 10:13, Jörn Zaefferer <joern.zaeffe...@googlemail.com> wrote: > How is the name attribute > invalid?http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_ext... > > Jörn > > On Thu, Mar 5, 2009 at 10:06 AM, zemm <simonenast...@gmail.com> wrote: > > > Hi, > > using jquery validate plugin seems that I can't avoid to use the > > "name" attribute in the text field for the captcha. > > Actually the validate plugin's remote method allows to send custom > > data, adding a "data" object: > > remote:{ > > url:"captcha_ck.php", > > type: "post", > > data:{ > > > > security_code: function() { > > return > > jQuery("#security_code").val(); > > } > > } > > } > > > but seems that the plugin itself will always look for the "name" > > attribute. > > My actual workaround is assigning the name attribute via jquery on > > document.ready, and it works (I mean, the w3c xhtml validator > > validates), but I still think that using the remote method shouldn't > > force me to use an attribute not compatible with w3c. Am I doing > > something wrong - missed something?
