On Thu, 28 Jul 2011, Ian Hickson wrote (I'm replying to myself here...):
On Fri, 29 Apr 2011, Jonas Sicking wrote:
On Fri, Apr 29, 2011 at 3:42 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 29 Dec 2010, Mounir Lamouri wrote:
On 12/29/2010 07:41 AM, Ian Hickson wrote:
I actually
2011/7/28 Scott González scott.gonza...@gmail.com
There are essentially three choices (this applies to most new markup-driven
features):
1) Provide the information in the appropriate attributes and let the
browser do its thing.
2) Provide the information in a script and do everything via
On Wed, Jul 27, 2011 at 8:37 PM, Jukka K. Korpela jkorp...@cs.tut.fi wrote:
28.07.2011 03:21, Ian Hickson wrote:
A text input field could have a number of error conditions:
Indeed. Therefore it would be essential to be able to set the error message
for _each_ check that a browser is supposed
On Wed, Jul 27, 2011 at 11:37 PM, Jukka K. Korpela jkorp...@cs.tut.fiwrote:
28.07.2011 03:21, Ian Hickson wrote:
A text input field could have a number of error conditions:
Indeed. Therefore it would be essential to be able to set the error message
for _each_ check that a browser is
28.07.2011 12:16, Scott González wrote:
I agree that it's extremely important to be able to define error
messages per error condition, but it's not necessary to code all data
checking in JavaScript to achieve that today.
It's not, but if you cannot set the error messages in HTML, what's the
2011/7/28 Jukka K. Korpela jkorp...@cs.tut.fi
28.07.2011 12:16, Scott González wrote:
I agree that it's extremely important to be able to define error
messages per error condition, but it's not necessary to code all data
checking in JavaScript to achieve that today.
It's not, but if you
Your 13 example is a good argument against splitting between markup
and script. If the minimum value is updated in the html but not the
js, you get confused users. - I've seen the results of letting logic
get out of sync from error reporting, it isn't pretty.
On 7/28/11, Scott González
On Wed, Jul 27, 2011 at 5:21 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 29 Apr 2011, Jonas Sicking wrote:
On Fri, Apr 29, 2011 at 3:42 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 29 Dec 2010, Mounir Lamouri wrote:
On 12/29/2010 07:41 AM, Ian Hickson wrote:
I actually think that the
On Fri, 29 Apr 2011, Jonas Sicking wrote:
On Fri, Apr 29, 2011 at 3:42 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 29 Dec 2010, Mounir Lamouri wrote:
On 12/29/2010 07:41 AM, Ian Hickson wrote:
I actually think that the customerrormessage attribute that has
been suggested is a
28.07.2011 03:21, Ian Hickson wrote:
A text input field could have a number of error conditions:
Indeed. Therefore it would be essential to be able to set the error
message for _each_ check that a browser is supposed to do on the basis
of HTML markup alone. If this is not possible, it is
On Wed, 29 Dec 2010, Mounir Lamouri wrote:
On 12/29/2010 07:41 AM, Ian Hickson wrote:
One way to do this would be to make the invalid event implement an
interface with a function like setCustomErrorMessage(in DOMString
message). This string would then be displayed by the UA in its UI
On Fri, Apr 29, 2011 at 3:42 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 29 Dec 2010, Mounir Lamouri wrote:
On 12/29/2010 07:41 AM, Ian Hickson wrote:
One way to do this would be to make the invalid event implement an
interface with a function like setCustomErrorMessage(in DOMString
On 12/29/2010 07:41 AM, Ian Hickson wrote:
One way to do this would be to make the invalid event implement an
interface with a function like setCustomErrorMessage(in DOMString
message). This string would then be displayed by the UA in its UI
wherever it displays validation error messages.
On Wed, Dec 29, 2010 at 2:23 AM, Mounir Lamouri
mounir.lamo...@gmail.com wrote:
On 12/29/2010 07:41 AM, Ian Hickson wrote:
One way to do this would be to make the invalid event implement an
interface with a function like setCustomErrorMessage(in DOMString
message). This string would then be
On Mon, 20 Sep 2010, Shiv Kumar wrote:
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
On 20 Sep 2010, at 23:38, Shiv Kumar wrote:
For the first scenario I’d like to propose that we have a validationMessage
attribute
Attributes should be avoided for text to be presented to human beings, because
such text may need to be marked up, e.g. for changes in language (span lang),
for
for validations but
it does also keep continue the paradigm.
Shiv
http://exposureroom.com
-Original Message-
From: Benjamin Hawkes-Lewis [mailto:bhawkesle...@googlemail.com]
Sent: Wednesday, September 22, 2010 3:00 AM
To: Shiv Kumar
Cc: 'WHATWG'
Subject: Re: [whatwg] Form element invalid
(Re-sending this email which was only addressed to Aryeh by mistake.)
On 09/21/2010 09:43 PM, Aryeh Gregor wrote:
I think only Opera has UI at all), so it's best to just
not use it for now.
Firefox nightlies too. Will be in Firefox 4 beta 7.
On 09/21/2010 10:35 PM, Shiv Kumar wrote:
That
On Tue, Sep 21, 2010 at 4:35 PM, Shiv Kumar sku...@exposureroom.com wrote:
Come now Aryeh :). Imagine this scenario. On a web page/form, I'm asking the
user to enter her social security number and she sees a message You have to
specify a value, you're saying that sounds ok to you? Oh, and the
On 9/22/10 5:51 PM, Aryeh Gregor wrote:
On Tue, Sep 21, 2010 at 4:35 PM, Shiv Kumarsku...@exposureroom.com wrote:
Come now Aryeh :). Imagine this scenario. On a web page/form, I'm asking the user to enter her
social security number and she sees a message You have to specify a value, you're
On Wed, Sep 22, 2010 at 5:51 PM, Aryeh Gregor simetrical+...@gmail.com wrote:
Note that Firefox is buggy here
and treats setCustomValidity('') as setting the error message to ''
instead of removing it, as the spec says, but when that's fixed it
will work.
I take it back. Firefox and Opera do
And yes, you could always conceive of simple declarative
APIs that would do this stuff,
Hmm... so you admit, it's simple. That's a start!
but you just can't add those for every
single feature someone wants.
I guess not :) Even if it makes it simpler, more approachable and more useful.
Shiv
On 22 Sep 2010, at 16:14, Shiv Kumar wrote:
In principle sure,
Glad you agree on the principle.
But you already have attributes being used to present text to users.
HTML usually adopts the good pattern of putting human-readable text that might
benefit from markup in elements (e.g. label,
New features should perpetuate the good paradigm represented by the label
element, not the bad paradigm represented by the title attribute.
Ok, I get it. That makes sense
So can we have a errorLabel tag where the for attribute can point to the
control in question? Or is that going against the
On 09/22/2010 02:51 PM, Aryeh Gregor wrote:
data:text/html,!doctype htmlforminput name=x required
oninvalid=this.setCustomValidity(''); if (!this.validity.valid)
this.setCustomValidity('abcd') input type=submit/form
In a Firefox 4 nightly, when I click the submit button, the error is
just
On Wed, Sep 22, 2010 at 5:50 PM, Mounir Lamouri
mounir.lamo...@gmail.com wrote:
On 09/22/2010 02:51 PM, Aryeh Gregor wrote:
data:text/html,!doctype htmlforminput name=x required
oninvalid=this.setCustomValidity(''); if (!this.validity.valid)
this.setCustomValidity('abcd') input
I actually think that the customerrormessage attribute that has been
suggested is a decent solution too.
So it looks like Jonas and Mounir concur. That's great!
All you'd need to do
is install an event handler for the invalid event, and in that
handler do something like
On Mon, Sep 20, 2010 at 6:38 PM, Shiv Kumar sku...@exposureroom.com wrote:
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
That doesn't seem cryptic to me.
Come now Aryeh :). Imagine this scenario. On a web page/form, I'm asking the
user to enter her social security number and she sees a message You have to
specify a value, you're saying that sounds ok to you? Oh, and the next browser
will say something like, This
Scenario 1:
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.
On 2010-09-21 00:38, Shiv Kumar wrote:
Scenario 1:
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
...@lists.whatwg.org] On Behalf Of Roger Hågensen
Sent: Monday, September 20, 2010 7:03 PM
To: whatwg@lists.whatwg.org
Subject: Re: [whatwg] Form element invalid message
On 2010-09-21 00:38, Shiv Kumar wrote:
Scenario 1:
We now have the option define if an element is required and the form will
validate
32 matches
Mail list logo
