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 14049 - Can you avoid the awkward situation of different defaults (content vs idl) for the size attribute by simply moving the 1 or 4 part to the paragraph about display size and not saying anything about the default value of the size content attribute? That wou
Summary: Can you avoid the awkward situation of different defaults (content vs idl) fo...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: 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-09-06 17:24 UTC by contributor
Modified: 2011-10-19 23:02 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-09-06 17:24:28 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html
Multipage: http://www.whatwg.org/C#the-select-element
Complete: http://www.whatwg.org/c#the-select-element

Comment:
Can you avoid the awkward situation of different defaults (content vs idl) for
the size attribute by simply moving the 1 or 4 part to the paragraph about
display size and not saying anything about the default value of the size
content attribute?  That would be cleaner if the 1 or 4 values aren't used
anywhere else.

Posted from: 66.114.38.251
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0a2) Gecko/20110902 Firefox/8.0a2
Comment 1 Ian 'Hixie' Hickson 2011-10-19 23:01:56 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: Accepted
Change Description: see diff given below
Rationale: Not a bad idea.
Comment 2 contributor 2011-10-19 23:02:17 UTC 
Checked in as WHATWG revision r6705.
Check-in comment: Change the way this is phrased to try to make it less confusing.
http://html5.org/tools/web-apps-tracker?from=6704&to=6705