Closed
Bug 1270
Opened 26 years ago
Closed 26 years ago
'smaller' problem on sans-serif font
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Tracking
()
VERIFIED
FIXED
M4
People
(Reporter: paul.lebeau, Assigned: peterl-retired)
References
()
Details
Hi The above URL shows use of 'font-size: smaller' when the default body font has been changed to 11pt sans-serif (Arial). The problem is that the second bit of text doesn't actually look any smaller. The step down looks ok at 12pt, and is exaggerated at 10pt. So I suspect that there is some issues with the font size-choosing algorithm. I haven't noticed any problems when the default serif font is used. Of course it is possible that this is just a problem with the Windows font system. However the same test seems okay in NS4.X. As Peter L suggested in a news thread about this, the font does actually get slightly smaller - but not really noticeably. I compared pixels and the second 'SOME TEXT' is actually 4 pixels smaller in width than the first one (we loose one pixel in the O, X and one pixel each between the T & E and X & T), but there is no difference in height between the two. I thought at first that nglayout might have been using the default MS Sans Serif font rather than Arial - but this is not the case (see .../test3a.html where I explicitly set the font to Arial). If you can't reproduce it, a gif of what I get is at http://www.caverock.com/~paul/css/test3.gif Regards Paul LeBeau PS. nglayout build I was using originally was 981015, but I have since tested it on 981103 as well (same result).
Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•26 years ago
|
||
The CSS font-size: smaller is functionally equivalent to <FONT size=-1> in that
context. This is a deliberate divergency from Nav 4.x.
Now that the Windows font size rounding bug is fixed, there is indeed a 1 pixel
difference in height for the test text.
This is correct behavior.
Updated•26 years ago
|
QA Contact: 3847
Updated•26 years ago
|
QA Contact: 3847 → 4110
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 3•26 years ago
|
||
Verified.
You need to log in
before you can comment on or make changes to this bug.
Description
•