Closed
Bug 375073
Opened 18 years ago
Closed 17 years ago
Minimum height of a button is larger on FF3 than FF2
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
RESOLVED
FIXED
People
(Reporter: duncan.loveday, Assigned: dbaron)
References
Details
(Keywords: regression, testcase, Whiteboard: [dbaron-1.9:RwCo])
Attachments
(2 files, 1 obsolete file)
400 bytes,
text/html
|
Details | |
1.19 KB,
patch
|
roc
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070320 Minefield/3.0a3pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070320 Minefield/3.0a3pre
The height of a button, as set using <INPUT type="button" style="height:<value>px">, seems to have a minimum value of about 20px on FF3 whereas in FF2 there was a much smaller minimum, if any.
Reproducible: Always
Steps to Reproduce:
1. Open the attached test.html
2.
3.
Actual Results:
A series of buttons of differing heights are displayed. In FF3 all the buttons are at least 20px high. In FF2 they are all different heights.
Expected Results:
Unless setting small button heights is invalid in the standard, FF3 should behave as FF2.
Reporter | ||
Comment 1•18 years ago
|
||
Reporter | ||
Comment 2•18 years ago
|
||
Adding regression keyword....this has broken an existing layout in my app.
Keywords: regression
Comment 3•18 years ago
|
||
The regression range I found is:
20070117 works
20070118 broke
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=PhoenixTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-01-17+04%3A00%3A00&maxdate=2007-01-18+04%3A00%3A00&cvsroot=%2Fcvsroot
I suspect Bug 366722.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Updated•18 years ago
|
Flags: blocking1.9?
Assignee | ||
Comment 4•18 years ago
|
||
Is this a case that would be improved by separating GetPreferredWidgetSize and GetMinimumWidgetSize, or are we already sort of doing that here (by doing one for HTML and the other for XUL)?
Assignee | ||
Updated•18 years ago
|
Flags: blocking1.9? → blocking1.9+
Assignee | ||
Updated•18 years ago
|
Assignee: nobody → dbaron
Assignee | ||
Updated•17 years ago
|
Whiteboard: [dbaron-1.9:RwCo]
Priority: -- → P3
Assignee | ||
Comment 5•17 years ago
|
||
This makes GetMinimumWidgetSize no-op for HTML buttons on Windows. I don't think this is a good idea. The buttons do draw correctly a bit smaller than their supposed minimum, but they become unreasonable pretty quickly.
This does make us do the same thing as Firefox 2 for buttons on Windows.
There are some other possibilities: using TS_MIN instead of TS_TRUE, or trying to select the correct fonts before requesting the size.
Assignee | ||
Comment 6•17 years ago
|
||
I think this makes a little more sense -- I'd actually thought we had this code generically for all widgets, but we don't seem to.
That said, it has pretty much the same effect, since it lets the widgets get pretty small. But I suppose that's ok, and it's what this bug reporter is requesting. That said, his app will still break on Mac.
Attachment #288777 -
Attachment is obsolete: true
Attachment #288778 -
Flags: superreview?(roc)
Attachment #288778 -
Flags: review?(roc)
Attachment #288778 -
Flags: superreview?(roc)
Attachment #288778 -
Flags: superreview+
Attachment #288778 -
Flags: review?(roc)
Attachment #288778 -
Flags: review+
Assignee | ||
Comment 7•17 years ago
|
||
Fix checked in to trunk.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Flags: in-testsuite?
Assignee | ||
Comment 8•17 years ago
|
||
I filed bug 403934 on splitting GetMinimumWidgetSize.
You need to log in
before you can comment on or make changes to this bug.
Description
•