W3C home > Mailing lists > Public > www-style@w3.org > December 2014

Empty button baseline difference in IE/Firefox and WebKit browsers

From: Bogdan Brinza <bbrinza@microsoft.com>
Date: Fri, 12 Dec 2014 22:34:59 +0000
To: "www-style@w3.org" <www-style@w3.org>
Message-ID: <BLUPR03MB13351BF1E0062B2D1D50F95AF600@BLUPR03MB133.namprd03.prod.outlook.com>

Here is yet another interoperability issue we've found during IE compatibility investigations, that I would like to clarify with working group.

Consider the following simplified example - http://jsfiddle.net/x2vgt1xz/ - it looks to me that IE/Firefox sets empty element baseline as if the button had a content inside, while it looks like Chrome is treating the empty button as an empty inline element.

We have encountered this on http://www.sportsauthority.com - the site tries to fix this for WebKit browsers with a rule offsetting title by negative 10 pixels:

@media screen and (-webkit-min-device-pixel-ratio: 0) {
#header #utility #sli_search_1 {
                position: relative;
                top: -10px;

Which browsers behaves correctly and per spec in this case? Or is this one of the areas left to UA that has compatibility constraints for some legacy content?
Received on Friday, 12 December 2014 22:35:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:49 UTC