114510 - Odd table behaviour when text alignment is changed to right or left.

Status: RESOLVED WORKSFORME

(Core :: Layout: Tables, defect, P3)

Description

[TucsonTester1]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.6+)
Gecko/20011210 Netscape6/6.2.1+
BuildID:    2001121003

When two tables are created and the alignment for the first table is changed to
right justified, the second table vanishes.  A minimize/maximuze does not bring
it back, but setting it back to left justify does -- however, it is brought back
on the same line as the first table.

Reproducible: Always
Steps to Reproduce:
1. Launch Composer
2. Insert a table (accept the default values)
3. Insert a second table below the first (accept the default values)
4. Click to the left of the first table, and click on align: right on the toolbar
5. Click on align: left on the toolbar

Actual Results:  When step 4 is performed, the second table will vanish.  When
step 5 is performed it will reappear to the right of the first table.


Expected Results:  When an empty table is set to align: right but it has a width
of 100%, there should be noticeable change.  When it is set back to align left,
it should not cause the line below it to appear next to it.

Other odd things can happen with this bug.  After step 5 is performed, if the
cursor is clicked below the two tables and then to the left of the first table
again, a flashing cursor will appear between the two tables.  If align: right or
center is chosen, the second table will drop down one cell and will be uneven
with the first.

Comment 1

[Olav Vitters]

Attachment: Generated tables, first table is aligned right

I see this using 2001122608 Linux. It seems that the two tables are shown on
top of eachother. After saving the generated file and loading this in Browser,
the tables are still shown on top of eachother.

Comment 2

[Olav Vitters]

Lets try HTMLTables, because I could not reproduce this with a <div> (for Layout
component).

+ marking new and changing OS to All.

Could be related: bug 104948 (couldn't reproduce that bug)

Comment 3

[karnaze (gone)]

Temporarily moving to future until a milestone can be assigned. 

Comment 4

[karnaze (gone)]

mass reassign to default owner

Comment 5

[Kevin McCluskey (gone)]

-> P3:Future

Comment 6

[Erik Fabert]

WFM, I could not reproduce this in Composer following the steps in Comment #0 
and the testcase looks OK.