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 23893 - CSS: define <button> rendering better
Summary: CSS: define <button> rendering better
Status: RESOLVED MOVED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other All
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard: blocked awaiting response to comment ...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-22 23:00 UTC by Ian 'Hixie' Hickson
Modified: 2018-10-16 14:26 UTC (History)
6 users (show)

See Also:
annevk: needinfo? (jackalmage)

Attachments

Description Ian 'Hixie' Hickson 2013-11-22 23:00:03 UTC 
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.
Comment 1 Ian 'Hixie' Hickson 2014-01-07 00:00:33 UTC 
Tab, any ideas what should be specced here?
Comment 2 Simon Pieters 2018-10-16 14:26:50 UTC 
https://github.com/whatwg/html/issues/4081