<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal>Scenario 1:<o:p></o:p></p>
<p class=MsoNormal>We now have the option define if an element is required and
the form will validate the value such elements before submission. That’s
a step in the right direction. However, it so happens different implementation
do different things in the case when the validation return false.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Some browsers, have no visual indication (probably due to
lack of support at this time)<o:p></o:p></p>
<p class=MsoNormal>Some browsers will outline the field in question<o:p></o:p></p>
<p class=MsoNormal>Some will pop up a message under the field in question. The
message is something cryptic like “You have to specify a value”.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Scenario 2:<o:p></o:p></p>
<p class=MsoNormal>That’s one aspect I’d like to talk about. The
other aspect is that typically, you don’t want to show only one error as
a time to the end user. You want to show them all validation errors after
trying to submit the form one time (this is the common practice as well),
rather than forcing them to submit a form multiple times to discover validation
issues one by one. As you can imagine this is a nightmare for the end-user.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>For the first scenario I’d like to propose that we
have a validationMessage attribute (or some other name) that allows web
developers to specify a more appropriate (based on the type of input data required
and/or the input type such as text, url, email etc.), user friendly/business
friendly and creative error message rather than some unknown message (as
different vendors will likely have their own verbiage). <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>For the second scenario I guess the spec should be clear
about validating all fields? I’m not sure what the spec for this is (I
can’t seem to find anywhere that details the validation process for
forms).<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>What are your thoughts on the above?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Shiv<o:p></o:p></p>
<p class=MsoNormal><a href="http://exposureroom.com/">http://exposureroom.com</a><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>