This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
Tab, any ideas what should be specced here?
https://github.com/whatwg/html/issues/4081