Closed
Bug 537715
Opened 15 years ago
Closed 14 years ago
Some tall characters in <h2> exceed their bounding boxes
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jdawiseman, Unassigned)
Details
(Whiteboard: [CLOSEME 2011-1-30])
Attachments
(2 files)
Screen shot of test case 419919.
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6
On Mac Firefox 3.5.6, in <h2>, some tall characters (ÀÁÂÃÅÈÉÊÌÍÎÑÒÓÔÕÙÚÛ√Š) exceed their bounding boxes, and one (⁄) exceeds it width-wise. See following test case.
This was discovered whilst making attachment 419881 [details] for bug 537444.
Reproducible: Always
|
Reporter | |
Comment 1•15 years ago
|
||
|
|
Reporter | |
Comment 2•15 years ago
|
||
<html><body><table border="1">
<tr><td><p>Agrave</p></td><td><h2>À</h2></td></tr>
<tr><td><p>Aacute</p></td><td><h2>Á</h2></td></tr>
<tr><td><p>Acirc</p></td><td><h2>Â</h2></td></tr>
<tr><td><p>Atilde</p></td><td><h2>Ã</h2></td></tr>
<tr><td><p>Aring</p></td><td><h2>Å</h2></td></tr>
<tr><td><p>Egrave</p></td><td><h2>È</h2></td></tr>
<tr><td><p>Eacute</p></td><td><h2>É</h2></td></tr>
<tr><td><p>Ecirc</p></td><td><h2>Ê</h2></td></tr>
<tr><td><p>Igrave</p></td><td><h2>Ì</h2></td></tr>
<tr><td><p>Iacute</p></td><td><h2>Í</h2></td></tr>
<tr><td><p>Icirc</p></td><td><h2>Î</h2></td></tr>
<tr><td><p>Ntilde</p></td><td><h2>Ñ</h2></td></tr>
<tr><td><p>Ograve</p></td><td><h2>Ò</h2></td></tr>
<tr><td><p>Oacute</p></td><td><h2>Ó</h2></td></tr>
<tr><td><p>Ocirc</p></td><td><h2>Ô</h2></td></tr>
<tr><td><p>Otilde</p></td><td><h2>Õ</h2></td></tr>
<tr><td><p>Ugrave</p></td><td><h2>Ù</h2></td></tr>
<tr><td><p>Uacute</p></td><td><h2>Ú</h2></td></tr>
<tr><td><p>Ucirc</p></td><td><h2>Û</h2></td></tr>
<tr><td><p>frasl</p></td><td><h2>⁄</h2></td></tr>
<tr><td><p>radic</p></td><td><h2>√</h2></td></tr>
<tr><td><p>Scaron</p></td><td><h2>Š</h2></td></tr>
</table></body></html>
|
||
Comment 3•15 years ago
|
||
I don't think this is necessarily a bug. I'm not familiar with the details of the relevant specs, but the borders are presumably based on the "typographic bounding box" of the text, meaning the box defined by the origin and advance width of the text, and the nominal ascent and descent of the font. But glyphs may legitimately project beyond these bounds, in any or all directions, depending on the design of the typeface and on the ascent and descent that the designer has chosen to specify - these are NOT guaranteed to encompass the full extent of all the glyphs.
For a more extreme example, try:
data:text/html,<body style="font-family:zapfino;"><table border="1"><tr><td>fine font flourisĥes tested</td></tr></table></body>
Here, the initial "f" projects to the left beyond the border; the accented "h" projects upwards; and the final "d" projects to the right. I believe this is correct behavior; a border that grows to enclose all the "ink" of the glyphs would NOT be expected.
|
|
Reporter | |
Comment 4•15 years ago
|
||
Well, perhaps the ‘bug’ should be that the default typefaces should fit in their bounding boxes.
FWLIW, Safari 4.0.4 and Chrome 4.0.249.43 do not have accents protruding above; but Opera 10.10 does (Opera’s Zapfino causes all the non-t ascenders break above). None of these browsers forces ⁄ to fit: rightly so I suspect.
|
||
Comment 5•14 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
|
|
||
Comment 6•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•