234652 - Bold / italic first characters displayed on table border

Status: NEW

(Core :: Layout, defect)

Description

[石庭豐 (Seak, Teng-Fong)]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113

This bug is just a pricky cosmetic one.

The following test-case will draw two table cells and a word.  The "tail" of the
italic character 'f' is displayed on table border.

<table border=1>
<tr>
  <th align="left"><em>filename</em> </th>
<tr>
  <td><em>filename</em>
</table>

Reproducible: Always
Steps to Reproduce:





Since this test-case doesn't use CSS, I hesitated and finally didn't choose the
"Layout:Tables" component.  Hope I didn't do wrong.

Comment 1

[Boris Zbarsky [:bzbarsky]]

You did wrong.  This component is for painting issues.  If things are the wrong
sizes or in the wrong places, this is not the right component.

Anyway, this is a duplicate.  And has no usable testcase.  Please do not file
such bugs as NEW in the future....

Comment 2

[石庭豐 (Seak, Teng-Fong)]

For the first point, it wasn't clear for me what "paint" and "object" mean
exactly.  "object" is in the sense of <object>?  Or anything that's displayed,
like a character, a line, an image?

And "paint", what's the meaning?  Display?  Or is it related to SVG.

For the second point, what I've written IS the test-case.  But if you could work
only with test-case, no problem, I'll make up one.

Comment 3

[石庭豐 (Seak, Teng-Fong)]

Attachment: Part of letter 'f' displayed on the border.

Comment 4

[j.j.]

Works for me

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20061231 Minefield/3.0a2pre

Reporter, please close this, if you agree.

Comment 5

[石庭豐 (Seak, Teng-Fong)]

(In reply to comment #4)
> Works for me
> 
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20061231
> Minefield/3.0a2pre
> 
> Reporter, please close this, if you agree.

Sorry, j.j., I'm using Firefox 2.0.0.1 but the bug is still there.  I won't close it.

Comment 6

[j.j.]

Please ignore comment 4.
This is *not* fixed with 1.9a2.
(Comment in wrong bug, sorry for the spam)

Comment 7

[石庭豐 (Seak, Teng-Fong)]

No problem ;)

And oh, I forgot to say, Happy New Year

Comment 8

[石庭豐 (Seak, Teng-Fong)]

For the record:
As of october 2009 with FF 3.5.3, this bug is still here.

Comment 9

[石庭豐 (Seak, Teng-Fong)]

Attachment: bug-234652-table-cosmetic-bug-ff-vs-ie.png

Happy 10th anniversary to this bug!  Time to revive it :)

The attached image shows how I.E. copes with this cosmetic problem: it actually clips away anything outside the border, which, IMO, isn't a bad idea.

PS: It is worth noting that fonts have smoother edge in IE than in FF, but that's another bug.

Comment 10

[j.j.]

(In reply to 石庭豐 (Seak, Teng-Fong) from comment #9)
> bug-234652-table-cosmetic-bug-ff-vs-ie.png

> Happy 10th anniversary to this bug!  Time to revive it :)
I see exactly the same behaviour with Safari, Chrome, IE8, 9, 10, 11.

> The attached image shows how I.E. copes with this cosmetic problem: it
> actually clips away anything outside the border, which, IMO, isn't a bad
> idea.
I see this clipping in IE6 and IE7 only.

> PS: It is worth noting that fonts have smoother edge in IE than in FF, but
> that's another bug.
I don't see that on Win XP. Please check anti-aliasing settings of your OS.

After all, we might dislike this bug, but we have large interoperability and should probably close it as INVALID (or should dup it to the underlying bug, which I can't find).

Comment 11

[j.j.]

> I see this clipping in IE6 and IE7 only.

... in standards mode

I see clipping in IE6, 7, 8, 9, 10, but no clipping in IE11
in quirks mode

Comment 12

[石庭豐 (Seak, Teng-Fong)]

(In reply to j.j. (mostly inactive) from comment #10)

> > PS: It is worth noting that fonts have smoother edge in IE than in FF, but
> > that's another bug.
> I don't see that on Win XP. Please check anti-aliasing settings of your OS.
> 
> After all, we might dislike this bug, but we have large interoperability and
> should probably close it as INVALID (or should dup it to the underlying bug,
> which I can't find).

By *this bug*, are you talking about this very bug, ie non-clipping bug?  Or the other bug, ie anti-aliasing bug?

And why should you/we close it as INVALID?  It's a cosmetic problem, isn't it?  Closing it as INVALID does not mean it's not there.  It just means Ostrich Policy is used to "solve" problem, which, IMO, is a very bad sign to give to Mozilla users.

PS: Oh yes, IE11 on Win7 indeed shows non-clipping bug.  But IMO, this is a regression.  I have filed a bug to Microsoft support.