This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
adding the list attribute to the input states that support it changes the control from a text box to a combo box. The table of types should reflect this.
mass-move component to LC1
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: Did Not Understand Request Change Description: no spec change Rationale: I don't understand. Could you elaborate? How is a combo box not a text box?
combobox and textbox are different roles in the accessibility APIs. For example, in UIA Edit Control Type: Edit controls enable a user to view and edit a simple line of text without rich formatting support. (similar to <input type=text>) ComboBox Control Type: A combo box is a list box combined with a static control or an edit control that displays the currently selected item in the list box portion of the combo box. (similar to <select>) When the author adds a list attribute, it adds a dropdown list to the control, which makes it meet the definition of the combobox.
HIxie, I reassigned this back to you because Cynthia has since responded to your request for me information; see her response in comment #3: > combobox and textbox are different roles in the accessibility APIs. For > example, in UIA > Edit Control Type: Edit controls enable a user to view and edit a simple line > of text without rich formatting support. (similar to <input type=text>) > > ComboBox Control Type: A combo box is a list box combined with a static control > or an edit control that displays the currently selected item in the list box > portion of the combo box. (similar to <select>) > > When the author adds a list attribute, it adds a dropdown list to the control, > which makes it meet the definition of the combobox.
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: Did Not Understand Request Change Description: no spec change Rationale: I'm still at a loss as to which table you're referring to. Do you mean the ARIA implicit roles table? That's the only place I see that uses ARIA terms here. It seems to use the role "combo" correctly though. I don't see anywhere that uses "textbox" incorrectly either.
This table: http://dev.w3.org/html5/spec/the-input-element.html#attr-input-type Though, yes, it should be in the aria table too. Keyword: text (added column) attributes: list data type: (no change) control type: Combo Box This is true for input type that normally renders as a text field, but gets a suggestion list with a list attribute. These include: text, search, tel, url, email, and number.
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: If you're asking to make that non-normative table more complicated purely so that we can indicate that some of the form controls are sometimes combination text+list boxes ("combo" boxes) rather than regular text boxes, then I think that would be a mistake. The table is already hard to understand as it is.
The HTML Accessibility TF Bug Triage sub team discussed this issue and determined that it remains valid and should be opened against HTML 5.1: http://www.w3.org/2014/02/12-a11y-bugs-minutes.html#item04 This issue is editorial.
This bug was discussed in the Bug Triage Sub-group on 25 JUNE 2014: http://www.w3.org/2014/06/25-a11y-bugs-minutes.html#item03 The TF and the bug triage sub team still believe this is a valid bug and a simple editorial fix. Perhaps the enumerated attributes table is not the right vehicle for clarifying how the list attribute affects the control type of certain elements. An alternative solution would be to simply add a footnote reference on the text, search, tel, url, email, and number attributes that explains how the control type changes to combo box if the list attribute is included. Moving to HTML5.1 component.
Triaged, needs to be done, awaiting the time when HTML can be edited rationally
Migrated to HTML: https://github.com/w3c/html/issues/174