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 13556 - why does the 'placeholder label option' on a select have to be the first 'option' within the list of options? could it be the first option with value="" within the list of options instead?
Summary: why does the 'placeholder label option' on a select have to be the first 'opt...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 02:06 UTC by contributor
Modified: 2011-08-14 06:06 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-08-03 02:06:43 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html
Multipage: http://www.whatwg.org/C#placeholder-label-option
Complete: http://www.whatwg.org/c#placeholder-label-option

Comment:
why does the 'placeholder label option' on a select have to be the first
'option' within the list of options? could it be the first option with
value="" within the list of options instead?

Posted from: 203.94.186.74
User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Comment 1 Tab Atkins Jr. 2011-08-03 02:11:55 UTC 
The whole point of a placeholder is that it's displayed by default.  The first <option> in a <select> is displayed by default, so it's the only one that makes sense to become a placeholder if you're attempting to optimize for backward compat.
Comment 2 Michael[tm] Smith 2011-08-04 05:13:37 UTC 
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-14 06:06:34 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: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand the proposal. Could you elaborate?