This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9280 - forms: Add default button option/attribute for forms
Summary: forms: Add default button option/attribute for forms
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC All
: P3 enhancement
Target Milestone: Needs Impl Interest
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://www.w3.org/Bugs/Public/show_b...
Whiteboard:
Keywords: a11y
: 13320 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-19 12:10 UTC by Jonathan Avila
Modified: 2017-07-21 10:32 UTC (History)
13 users (show)

See Also:


Attachments

Description Jonathan Avila 2010-03-19 12:10:18 UTC
Please consider adding a default button option/attribute for forms.  I believe this would simplify a lot of form interaction for users of assistive technology and users who rely off of the keyboard alone.  Currently different browsers
handle this differently and there is no specific method for assigning which button will be activated when enter is pressed in a form field other than a button that works across browsers.
Comment 1 Ian 'Hixie' Hickson 2010-04-01 22:24:03 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: The spec defines how default buttons are to be selected:

   http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#default-button

I agree that we should probably make it possible to explicitly pick a button as the default. However, we've already added quite a lot to the forms part of the spec and not all of it has been widely implemented yet, so I'd rather we wait some more before adding such a feature.
Comment 2 Michael Cooper 2010-08-31 14:06:11 UTC
http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0124.html

The bug triage sub-team believes the HTML A11Y TF should take up this bug. Additional notes may follow in a separate comment.
Comment 3 Michael Cooper 2010-09-02 13:15:05 UTC
Bug triage sub-team says declarable default submit button would be a good a11y enhancement.
Comment 4 Anne 2011-08-14 09:59:35 UTC
*** Bug 13320 has been marked as a duplicate of this bug. ***
Comment 5 public-rdfa-wg 2013-01-24 06:53:12 UTC
This bug was cloned to create HTML WG bug 19046.
Comment 6 Ian 'Hixie' Hickson 2013-03-18 22:36:59 UTC
Are any browsers interested in implementing a "this is the default submission button" attribute for web forms, or is the current model ("first") sufficient for most purposes?
Comment 7 Anne 2015-09-16 11:40:13 UTC
Olli, Paul, any interest in this or knowing who we should ask?
Comment 8 Olli Pettay 2015-09-16 18:00:53 UTC
I don't have strong opinions on this. "first" kind of makes sense to me, so I'd like to understand why we'd need this complication.
Comment 9 Anne 2015-09-17 09:19:20 UTC
Olli, I think the reason is that it's still left up to the underlying platform which button is the default. "First" is just strongly suggested.
Comment 10 Anne 2017-07-21 10:32:52 UTC
Please file a new issue at https://github.com/whatwg/html/issues/new if there's still interest.