Posted by member 12025 on 2003-11-30 18:14:51 link
All that there really appearts to be is that it doesn't like the TR and TABLE being closed.
The width it offsets is clearly 100%. So is the width of the table where it starts the offset.
1. OK, so there's table at 100% width.
2. There's a cell in that table that is then (erroneously?) caused to span that 100% width.
3. Then, beside it, in the next cell, is another table, also 100%, told to span another 100% of the parent width.
I wish I could make this problem occur offline, though.
Also, the errors after the one for INPUT are a bit odd. Unfortunately I don't have the means nor caffiene level to see if those tags are indeed not open somewhere.
The width it offsets is clearly 100%. So is the width of the table where it starts the offset.
1. OK, so there's table at 100% width.
2. There's a cell in that table that is then (erroneously?) caused to span that 100% width.
3. Then, beside it, in the next cell, is another table, also 100%, told to span another 100% of the parent width.
I wish I could make this problem occur offline, though.
Also, the errors after the one for INPUT are a bit odd. Unfortunately I don't have the means nor caffiene level to see if those tags are indeed not open somewhere.