Bug 69065 – HTML5 forms having single input box & disabled submit button gets submitted implicitly on enter

• Status: RESOLVED
• Resolution: WONTFIX
• Component: Forms

[Kaustubh Atrawalkar]

Created attachment 109127 [details]
Test Case

A HTML5 form having only one input box and disabled (but visible) Submit button do get submitted on enter key press.
Rationale - 

Safari (WebKit) - Submits form
MSIE - Submits form
Firefox - Do not submit
Opera - Do not submit

[Alexey Proskuryakov]

> Safari (WebKit) - Submits form
> MSIE - Submits form

Sounds like WONTFIX then.

[Kaustubh Atrawalkar]

But this seems to be followed up approach. As per the specs there is clear guideline mentioned - http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#implicit-submission

"Note:Consequently, if the default button is disabled, the form is not submitted when such an implicit submission mechanism is used. (A button has no activation behavior when disabled.)"

[Kaustubh Atrawalkar]

Created attachment 109151 [details]
Patch

Patch for disabling submission for form having single input box & disabled submit button.

[Kaustubh Atrawalkar]

Created attachment 109152 [details]
Patch

Missed updated test case results. Updated.

[Alexey Proskuryakov]

Comment on attachment 109152 [details]
Patch

We cannot flip behavior back and fourth every time a contributor disagrees with the previous choice. If you svn blame test line that says "match IE, not FF", you'll find that it was investigated very recently, and we went with IE behavior intentionally.

If we take this patch, what should stop us from taking a patch that reverts the behavior to IE compatible a few months later?

[Kaustubh Atrawalkar]

(In reply to comment #5)
> (From update of attachment 109152 [details])
> We cannot flip behavior back and fourth every time a contributor disagrees with the previous choice. If you svn blame test line that says "match IE, not FF", you'll find that it was investigated very recently, and we went with IE behavior intentionally.
> 

I don't want to make it flip and change the behaviour. It was just when I was working on forms I happened to see this behaviour. I agree that this change was made intentionally to match IE  and without knowing that It was not worth to change it again.

> If we take this patch, what should stop us from taking a patch that reverts the behavior to IE compatible a few months later?

I think this would be WONTFIX then.