23893 2013-11-22 23:00:03 +0000 CSS: define <button> rendering better 2018-10-16 14:26:50 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other All RESOLVED MOVED blocked awaiting response to comment 1 (please remove this when replying) P3 normal Unsorted 1 ian ian annevk ian jackalmage mike w3bugs zcorpan contributor oldest_to_newest 96733 0 ian 2013-11-22 23:00:03 +0000 We should define the rendering of <button>. It's not a replaced element (rendering of contents is CSS-defined). It does respond to 'display', just not as you'd expect. For example, setting it to display:table doesn't make it a table on the inside: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2650 Setting it to 'table-row' doesn't make it a row on the outside: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2651 Setting it to 'display:block' does seem to make a difference, though: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2652 ...so it's not always display:inline-block (which is what the spec currently says). Browsers (I mainly tested Gecko and WebKit) are remarkably interoperable around this. Not sure what to spec here exactly. 98057 1 ian 2014-01-07 00:00:33 +0000 Tab, any ideas what should be specced here? 129352 2 zcorpan 2018-10-16 14:26:50 +0000 https://github.com/whatwg/html/issues/4081