12659 2011-05-15 06:19:47 +0000 The list is missing "input, select { display: inline-block; }", which is present in the CSS 2.1 stylesheet and supported by browsers. 2011-08-31 23:53:07 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#display-types P3 normal --- 1 contributor ian annevk bzbarsky ian jackalmage mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 48520 0 contributor 2011-05-15 06:19:47 +0000 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 48521 1 bzbarsky 2011-05-15 11:08:09 +0000 "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? 48522 2 jackalmage 2011-05-15 17:04:01 +0000 Consistency, both between browsers and with the CSS2.1 recommended style sheet. 48523 3 bzbarsky 2011-05-15 17:05:46 +0000 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. 53939 4 mike 2011-08-04 05:34:40 +0000 mass-move component to LC1 55208 5 annevk 2011-08-16 08:47:14 +0000 Not going to resolve this as WONTFIX as I work for Opera, but I agree with Boris. 56137 6 ian 2011-08-31 23:53:07 +0000 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.