#7077 closed bug (wontfix)

Opened March 07, 2011 02:52PM UTC

Closed October 15, 2012 06:52PM UTC

Button: Inconsistent button height in IE6

Reported by: Necroman Owned by: Necroman
Priority: minor Milestone: 1.11.0
Component: ui.button Version: 1.8.10
Keywords: Cc:
Blocked by: Blocking:
Description

When creating button with icon from <button> using jQuery .button({icons: {primary: icon}} method, the rendered height is different in current browsers vs IE6, even when using standard mode (not quirks). More specifically the height in IE6 is no less then 28px, in other browsers it's about 25px. I can't even use style with height:25px!important - it's not applied in IE6.

This is a major problem for me - the solution is either use exactly 28px height buttons, or use custom made buttons.

See this picture - left: IE6, right: Opera

[[Image(http://img64.imageshack.us/img64/1570/captureyov.jpg)]]

Attachments (0)
Change History (5)

Changed March 07, 2011 02:59PM UTC by scottgonzalez comment:1

owner: → Necroman
status: new → pending

What is your line-height set to?

Changed March 07, 2011 03:42PM UTC by Necroman comment:2

_comment0: Test demo here: http://einstein.php5.cz/button/test.html \ For testing in IE6 use either http://www.my-debugbar.com/wiki/IETester/HomePage or quirk mode in IE9 → 1299512670521173
status: pending → new

Test demo here: http://einstein.php5.cz/button/test.html

For testing in IE6 use either http://www.my-debugbar.com/wiki/IETester/HomePage or IE6 document mode in IE9

Changed September 08, 2011 04:36AM UTC by AlistairB comment:3

I have the same bug. Adding overflow:hidden; fixed the problem in IE6 for me.

Changed October 11, 2012 02:43PM UTC by scottgonzalez comment:4

milestone: 1.9.0 → 1.11.0

Changed October 15, 2012 06:52PM UTC by bchiasson comment:5

resolution: → wontfix
status: new → closed
summary: Incorect height of Button in IE6 → Button: Inconsistent button height in IE6

AlistairB resolved the issue using overflow:hidden. The team is dropping IE6 support in 1.10, so unfortunately we will not be resolving this issue.