<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 2010-09-21 00:38, Shiv Kumar wrote:
<blockquote cite="mid:006301cb5914$9b35bf80$d1a13e80$@com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<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]-->
<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?</p>
<br>
</div>
</blockquote>
<br>
Hmm! Like a error="" attribute or something like that, which is
shown instead of a generic built in browser message?<br>
<br>
Take this example <a class="moz-txt-link-freetext" href="http://www.quirksmode.org/dom/error.html">http://www.quirksmode.org/dom/error.html</a><br>
<br>
<br>
I assume you wish to be able to do this instead:<br>
<input size="20" name="email" id="email" error="A valid email
must be entered!" type="email" required><br>
<br>
and that if it is: <input size="20" name="email" id="email"
error="" type="email" required><br>
or if it is <input size="20" name="email" id="email" type="email"
required><br>
then the built in browser error message for type="email" should be
shown?<br>
<br>
This still leaves the question of where/how to display the error.<br>
Some might want a Balloontip happening when the field looses focus
(this is how the Windows OS does it) and saves the most IMO, the
error text could be shown then.<br>
<br>
If the browser does not behave like that but only when pressing
submitting then marking the fields and perhaps provide a mouseover
tip explaining the error (the error text could be shown then)<br>
<br>
Or the error text could be shown like in that example, but that wold
require a "errorfor" or similar to how label for behaves.<br>
<br>
<br>
I think it would be just best to spec it so that a Balloontip with
the browser error message (or the input field's custom error
message) is displayed at the field loosing focus, and optionally
keeping the field highlighted until the input is acceptable, thus
allowign the user to fill out the rest of the form and fix the error
last, and not allow submission unless all errors are fixed
obviously, and if no fields been filled and the user tries to submit
then all required fields would be highlighted, maybe a default OS
error "ding" should be played too.<br>
<br>
I believe this is the best UI implementation as it's instant
feedback based.<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Roger "Rescator" Hågensen.
Freelancer - <a class="moz-txt-link-freetext" href="http://EmSai.net/">http://EmSai.net/</a>
</pre>
</body>
</html>