236884 - The text is not properly positioned in the table cells.... Arabic encoding

Status: RESOLVED DUPLICATE of bug 174470

(Core :: Layout: Tables, defect)

Description

[Orc King]

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

In the page http://www.shrc.org/arabic/communications/reports/2004/archive2004.htm
The table cells are not properly positioned
maybe the Arabic encoding will make a difference becuase it is right to left

It works fine in IE

Reproducible: Always
Steps to Reproduce:
1.Go to http://www.shrc.org/arabic/communications/reports/2004/archive2004.htm
2.
3.



Expected Results:  
Positioned the text properly in the cells

Comment 1

[José Jeria]

Looks good with build 20040302, Windows XP, better than IE actually.

Please retest with a nightly build.

Comment 2

[Wayne Woods]

I'm using the latest nightly build and it looks wrong to me (both Mac and Windows).

I assume the narrow column of the table is supposed to be on the right, where
the 2004... etc text is? That's the way it appeared in IE, to me. Instead, it's
on the left, and the wide body of text runs between the left and right cells.

Comment 3

[Wayne Woods]

Attachment: Reduced test case showing bad table borders for rtl text when border-collapse is used

Check out the attachment, which uses standard Latin text, but still displays
the problem. Essentially there's a table with two cells: one containing a short
string of As, and the other a long string of Bs, but the cell widths for the
two strings are swapped.

If I remove either  dir="rtl" OR style="border-collapse: collapse;" then the
problem goes away. So it's a combination of the rtl text direction, and the
border-collapse property.

This problem also exists in Mozilla Seamonkey, and I've managed to find a
duplicate: bug 174470. It looks like the fix is far from simple, but they're
working on it.

Comment 4

[Wayne Woods]

*** This bug has been marked as a duplicate of 174470 ***