- From: Kaustubh Atrawalkar <kaustubh@motorola.com>
- Date: Thu, 29 Sep 2011 12:20:46 +0530
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. > > Reopening discussion - In case of single Input box and disabled (but visible button) forms still gets submitted on implicit submission. This is again something weird and happens in IE & Webkit but not in FF & opera. IMHO, the implicit submission should have straight away algorithm - 1) If submit button is there but not disabled implicit submission should happen on enter key press 2) If submit button is there and disabled implicit submission should not happen on enter key press Both logic should be irrespective of number of input button OR visibility of submit button. - Kaustubh
Received on Wednesday, 28 September 2011 23:50:46 UTC