Re: [WSG] XHTML Standard question
OK. For the last almost 24 hours, I have been trying to get the link to the results posted on the server to work, but have failed miserably. The results were made public to subscribers of the newsletters they mail out every month. They have not yet decided to use the Internet to mail out the newsletters. Just post and allow pay-per-one-time-view. I had to request permission to have a free link up this time. Now the server will not cooperate. Still working on it. To Luke, I did make a mistake in the way I read what was said. They have it turned on by default but would PREFER not to. And to Ben, I read what you posted and the links as well, thanks. I guess I just didn't pay enough attention when searching. On Wed, Nov 19, 2008 at 9:47 PM, Ben Buchanan [EMAIL PROTECTED] wrote: So exactly what behavior is mandated for UAs implementing HTML5 if a form is submitted with a 'required' element unsatisfied? If I'm reading http://www.whatwg.org/specs/web-forms/current-work/#required0 correctly, the form just won't submit if a required field is empty. Not sure about the UI feedback and so on, although looking at http://www.whatwg.org/specs/web-forms/current-work/#form-submission I think the onus will be on the developer to handle error feedback (ie. same as now). cheers, Ben -- --- http://weblog.200ok.com.au/ --- The future has arrived; it's just not --- evenly distributed. - William Gibson *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Brett P. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] XHTML Standard question
I know that most, if not possible to say all, Web page designers use JavaScript for form validation. During a recent poll done by a few local colleges, 41.2% of the people who responded stated that they would rather not have to enable JavaScript, but on rare occasion they do for certain sites that require JS for use of their forms to buy or sign up for something. After reading this, I did some research, and could not find any tag attributes for form elements that would not require the use JS for form validation. Therefore, I was wondering if it would be feasible to include a standard that would use a syntax similar (does not actually *have* to be this way) to selected=selected? In which case, the syntax would be required=required. Or, if it is an email input (i.e. Your e-mail address:input type=text required=required; include:@ /). -- Brett P. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] XHTML Standard question
Remember to use server side validation and you don't need to worry about rewriting standards :) Brett Patterson wrote: I know that most, if not possible to say all, Web page designers use _javascript_ for form validation. During a recent poll done by a few local colleges, 41.2% of the people who responded stated that they would rather not have to enable _javascript_, but on rare occasion they do for certain sites that require JS for use of their forms to buy or sign up for something. After reading this, I did some research, and could not find any tag attributes for form elements that would not require the use JS for form validation. Therefore, I was wondering if it would be feasible to include a standard that would use a syntax similar (does not actually have to be this way) to selected="selected"? In which case, the syntax would be required="required". Or, if it is an email input (i.e. Your e-mail address:input type="text" required="required; include:@" /). -- Brett P. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] XHTML Standard question
OK. I had forgotten you could use server-side validation. Thanks. On Wed, Nov 19, 2008 at 6:52 PM, Anthony Ziebell [EMAIL PROTECTED] wrote: Remember to use server side validation and you don't need to worry about rewriting standards :) Brett Patterson wrote: I know that most, if not possible to say all, Web page designers use JavaScript for form validation. During a recent poll done by a few local colleges, 41.2% of the people who responded stated that they would rather not have to enable JavaScript, but on rare occasion they do for certain sites that require JS for use of their forms to buy or sign up for something. After reading this, I did some research, and could not find any tag attributes for form elements that would not require the use JS for form validation. Therefore, I was wondering if it would be feasible to include a standard that would use a syntax similar (does not actually *have* to be this way) to selected=selected? In which case, the syntax would be required=required. Or, if it is an email input (i.e. Your e-mail address:input type=text required=required; include:@ /). -- Brett P. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Brett P. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] XHTML Standard question
Hi, What was the poll and are the results publicly available? There is a difference in asking if a user would like to have javascript turned off and them actually having it turned off, check: http://www.thecounter.com/stats/2008/November/javas.php only 6% have it off, and many of these will be down to their browser not supporting js (phones and older browsers). You do use server side validation on all forms, in addition to any js... right? cheers Luke Brett Patterson wrote: I know that most, if not possible to say all, Web page designers use JavaScript for form validation. During a recent poll done by a few local colleges, 41.2% of the people who responded stated that they would rather not have to enable JavaScript, but on rare occasion they do for certain sites that require JS for use of their forms to buy or sign up for something. After reading this, I did some research, and could not find any tag attributes for form elements that would not require the use JS for form validation. Therefore, I was wondering if it would be feasible to include a standard that would use a syntax similar (does not actually *have* to be this way) to selected=selected? In which case, the syntax would be required=required. Or, if it is an email input (i.e. Your e-mail address:input type=text required=required; include:@ /). -- Brett P. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] XHTML Standard question
Therefore, I was wondering if it would be feasible to include a standard that would use a syntax similar (does not actually *have* to be this way) to selected=selected? In which case, the syntax would be required=required. Or, if it is an email input (i.e. Your e-mail address:input type=text required=required; include:@ /). The stats you quoted do seem quite high - I'd be interested to see the full questions etc to see if there was some further context. Anyway, that aside... I would suggest that you follow the hijax approach and build your form with server-side validation to back up js validation (eg. if you're using PHP, Y Validate might be suitable for you http://www.sitepoint.com/article/javascript-just-not-validation/). Looking to the future, HTML5 is introducing a simple required attribute: The new required attribute applies to input (except when the type attribute is hidden, image or some button type such as submit) and textarea. It indicates that the user has to fill in a value in order to submit the form. [http://www.w3.org/TR/html5-diff/#new-attributes] Obviously that just requires *something* to be entered and doesn't validate the actual input; but it will still make life easier. Plus, of course, being HTML5 it could be quite some time before we see a level of browser implementation that would let us go ahead and use it. But it's good to know it's in the plan :) cheers, Ben -- --- http://weblog.200ok.com.au/ --- The future has arrived; it's just not --- evenly distributed. - William Gibson *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] XHTML Standard question
So exactly what behavior is mandated for UAs implementing HTML5 if a form is submitted with a 'required' element unsatisfied? If I'm reading http://www.whatwg.org/specs/web-forms/current-work/#required0correctly, the form just won't submit if a required field is empty. Not sure about the UI feedback and so on, although looking at http://www.whatwg.org/specs/web-forms/current-work/#form-submission I think the onus will be on the developer to handle error feedback (ie. same as now). cheers, Ben -- --- http://weblog.200ok.com.au/ --- The future has arrived; it's just not --- evenly distributed. - William Gibson *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
