[whatwg] HTMLForms: Implicit Submission with {display:none} button

Ryosuke Niwa rniwa at webkit.org
Fri Dec 9 15:06:37 PST 2011

Given that both IE and WebKit have been disabling implicit form submission
for years when the button has display: none, I don't think we can change
our behavior here.

Ryosuke Niwa
Software Engineer
Google Inc.

On Wed, Oct 12, 2011 at 11:33 PM, Kaustubh Atrawalkar <kaustubh at motorola.com
> wrote:

> On Mon, Sep 26, 2011 at 2:36 AM, Glenn Maynard <glenn at zewt.org> wrote:
>> On Sun, Sep 25, 2011 at 1:02 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:
>>>  The current Trident/WebKit behavior has a nice side-effect to (without
>>> scripts) require a visible submit button to enable implicit form submission.
>> I don't find that nice.  As a user, it's very annoying when implicit form
>> submission doesn't work for some obscure reason (like not having a submit
>> control), forcing me to use the mouse instead of it behaving like any other
>> form.  It makes the UI inconsistent and unpredictable.
>> Also, the single-text-input-with-no-submit-button case doesn't follow the
>> above.
>> The "without scripts" is also a fatal caveat.  Users can't be expected to
>> understand things like "you can press enter to submit the form if you see a
>> browser-native submit button, but not if the button is actually scripted
>> markup".
>> In principle, *all* forms should allow implicit submit, unless the site
>> explicitly doesn't want it (scripted autosave dialogs) or the UA doesn't
>> support it.  That ship sailed years ago, but the visibility of the submit
>> button shouldn't enter into it.
> Should this be made to for all browser compliance and browser to allow
> implicit submission irrespective of visibility of submit button? A web-dev
> can always stop this by either disabling the submit button or through
> script. Browser can give control back to onsubmit handler on enter key
> press if there is enabled submit button.

More information about the whatwg mailing list