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 12659 - The list is missing "input, select { display: inline-block; }", which is present in the CSS 2.1 stylesheet and supported by browsers.
Summary: The list is missing "input, select { display: inline-block; }", which is pres...
Status: RESOLVED WONTFIX
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-05-15 06:19 UTC by contributor
Modified: 2011-08-31 23:53 UTC (History)
7 users (show)

See Also:

Attachments

Description contributor 2011-05-15 06:19:47 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/rendering.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#display-types

Comment:
The list is missing "input, select { display: inline-block; }", which is
present in the CSS 2.1 stylesheet and supported by browsers.

Posted from: 76.253.3.102
User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Comment 1 Boris Zbarsky 2011-05-15 11:08:09 UTC 
"Supported by browsers" in what sense?  The default display if <input> and <select> seems to be 'inline-block' in WebKit and Trident, but 'inline' in Presto and Gecko.  Furthermore, the layout is the same in either case, since it's a replaced element.  So what benefit is there to having this rule?
Comment 2 Tab Atkins Jr. 2011-05-15 17:04:01 UTC 
Consistency, both between browsers and with the CSS2.1 recommended style sheet.
Comment 3 Boris Zbarsky 2011-05-15 17:05:46 UTC 
I agree consistency between browsers is desirable, but why is consistency in favor of adding the rule as opposed to it being removed in the UAs that seem to have.

Consistency with the CSS2.1 stylesheet should imo be a non-goal; it's got way too many issues last I looked.
Comment 4 Michael[tm] Smith 2011-08-04 05:34:40 UTC 
mass-move component to LC1
Comment 5 Anne 2011-08-16 08:47:14 UTC 
Not going to resolve this as WONTFIX as I work for Opera, but I agree with Boris.
Comment 6 Ian 'Hixie' Hickson 2011-08-31 23:53:07 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: inline-block seems pointless here. Adding a rule that does nothing is just bloat.