On 29 sep 2011, at 18:25, Jonas Sicking wrote:
I agree that this sounds like a good idea.
One simple solution would be to make checkValidity take a optional
boolean argument which defaults to false. If the function is called on
a form and passed true, this instructs the UA to display the
On 29 sep 2011, at 02:25, Jonas Sicking wrote:
OK, I understand... so is there a reason not to have a method for triggering
the display of validation errors in addition to triggering a click on a
submitControl? (I can understand not wanting duplication of functionality,
but it would be
On Thu, Sep 29, 2011 at 12:32 AM, Matias matia...@gmail.com wrote:
On 29 sep 2011, at 02:25, Jonas Sicking wrote:
OK, I understand... so is there a reason not to have a method for
triggering the display of validation errors in addition to triggering a
click on a submitControl? (I can
Hi Mounir and sorry for the late reply,
1) Is there a reason why native form validation seems to be tied to the
click of the submit button? Submitting the form using JavaScript does not
seem to trigger HTML5 form validation in either Firefox, Opera or the Webkit
browsers (I haven't checked
On 26/09/2011 14:35, Anne van Kesteren wrote:
On Mon, 26 Sep 2011 13:58:52 +0200, Matias matia...@gmail.com wrote:
1) Is there a reason why native form validation seems to be tied to
the click of the submit button? ...
What is the reason for wanting this?
I think this is exactly what this
On Wed, Sep 28, 2011 at 11:00 AM, Rob Crowther robe...@boogdesign.com wrote:
I think this is exactly what this StackOverflow user was asking for:
http://stackoverflow.com/questions/7548612
Basically he wants to trigger validation for each section of the form as the
user goes along.
Doesn't
On 28/09/11 19:59, Aryeh Gregor wrote:
Basically he wants to trigger validation for each section of the form as the
user goes along.
Doesn't Firefox already behave this way natively?
I don't think so but I'm happy to be corrected. How would it work, can
you have a submit button per
On Wed, Sep 28, 2011 at 6:56 AM, Matias matia...@gmail.com wrote:
Hi Mounir and sorry for the late reply,
1) Is there a reason why native form validation seems to be tied to the
click of the submit button? Submitting the form using JavaScript does not
seem to trigger HTML5 form validation
Hi,
I don't know if this can/should be specified in the spec or if it's up to the
browser implementors but here's some concerns I have regarding HTML5 form
validation;
1) Is there a reason why native form validation seems to be tied to the click
of the submit button? Submitting the form using
On Mon, 26 Sep 2011 13:58:52 +0200, Matias matia...@gmail.com wrote:
1) Is there a reason why native form validation seems to be tied to the
click of the submit button? Submitting the form using JavaScript does
not seem to trigger HTML5 form validation in either Firefox, Opera or
the Webkit
On 09/26/2011 01:58 PM, Matias wrote:
1) Is there a reason why native form validation seems to be tied to the click
of the submit button? Submitting the form using JavaScript does not seem to
trigger HTML5 form validation in either Firefox, Opera or the Webkit browsers
(I haven't checked how
Hi Anne,
The reason is I would love a simple and clear way to trigger form validation
(as well as displaying validation errors) programmatically in web apps. As the
current implementation stands, the submit button becomes a requirement if you
want to utilize native browser form validation.
Of
12 matches
Mail list logo
