225937 - When table is edited with composer, align="left" disappears.

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Samuel Blomqvist]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029

If I use Composer to edit the table on the site the part align="left" dissapears
from the <table>-tag and the right table moves from it's correct posittion on
the right of the main table to below the main table. If I choose "center" or
"right" in "Table properties" I see it in the tag  but when choosing "left"
nothing is there.

Reproducible: Always

Steps to Reproduce:
1.Open page in Composer
2.Edit the left table through the "Table properties" dialog (changing hight by
1px or something)
3.Watch the result

Actual Results:  
The align="left" part in the <table>-tag disapears and the right table moves to
below the left table.

Expected Results:  
The align="left" part in the <table>-tag stays or is added if it's not there.
And the right table stays where it belongs.

I know practicly nothing about creating webpages so if there is a fundamental
flaw in how this page is created I'm sorry. I just noted this strange behaviour
when I encouraged my friend to switch from a pirated version of Dreamweaver to
Mozilla Composer. For the moment I solve the problem by editing the table in
Composer and then adding the align="left" part manually in the source tab.

Comment 1

[Mats Palmgren (inactive)]

*** Bug 226914 has been marked as a duplicate of this bug. ***

Comment 2

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

I can't reproduce this bug.
Samuel, please, give more detailed instructions to reproduce the bug and
hälsningar från Paris...
Mats, please, next time you confirm a bug, please add a comment saying "I can
reproduce this bug as it is described above".

Comment 3

[Samuel Blomqvist]

Ok here goes a more detailed instruction.
1. Open http://www.corpus.umu.se/i2b.html in Composer and look at the layout
with one table on the left and one on the right with the text "Kårstyrelsens
  kalendarium ..."
2. check the "source tab". On line 10 it says <table height="1800" style="width:
428px; height: 1800px;" align="left" name="Huvudtable">
3. Go back to "Normal" right click in the left table and choose "Table Cell
Properties"
4. Reduce "Height" by 1 pixel. And choose OK.
5. check the layout again and see that the right table, the one with the text
"Kårstyrelsens kalendarium ..." has moved from it's place on the right to below
the first table.
6. check the "source tab" and see that on line 10 there is now: <table
name="Huvudtable" style="width: 428px; height: 1800px;"
height="1800">   The align="left" has dissapered.

I can choose to align the table to "center" or "right" and the tag is there (I
do this in the "table properties / Table Alignment" dropdown menu. but if I
choose "left" the tag is not there.

I hope this helps if not tell me what is unclear and I'll try again...

Comment 4

[Mike Cowperthwaite]

*** Bug 248763 has been marked as a duplicate of this bug. ***

Comment 5

[Mike Cowperthwaite]

The duplicate was reported under HTML mail composition, and I have reproduced it 
in that context with
  Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040623

However, in Composer, I am finding somewhat more complicated behavior, as 
described at bug 229846.

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420