W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2011

[whatwg] questions regarding submit event timing

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 2 May 2011 17:10:18 -0700
Message-ID: <BANLkTinoev9GyBdzftvwJiz9pZ9XeOq=8Q@mail.gmail.com>
On Sun, May 1, 2011 at 6:14 PM, Hallvord R M Steen <hallvors at gmail.com> wrote:
> Some questions related to possibly clarifying this section:
> http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#concept-form-submit
>
> 1) What methods exactly cause the "scripted submit" flag to be set?
> It's obviously set if you call form.submit(), but will it be set in
> these two cases:
>
> HTML: <form><input type="submit"></form>
> JS: form.elements[0].click()
>
> or
> HTML: <form><input type="submit"></form>
> JS: form.elements[0].dispatchEvent( evt ) /* where evt is a 'click'
> event object ?*/
>
> I believe the answer should be yes in both cases but I'm not sure if
> it's clear from the spec.
>
> 2) Is the event fired synchronously? (And is it fired synchronously
> for all three cases of scripted submits mentioned above?)
> Again, I think the answer is yes but I couldn't find this information
> in the spec when looking for it.

Isn't the purpose of this flag mostly backwards compatibility, but
otherwise a fairly awkward feature. If so, it seems like we should
limit its scope as much as possible, both to make implementation
easier, and to make the forms API otherwise as simple as we can.

/ Jonas
Received on Monday, 2 May 2011 17:10:18 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:32 UTC