On 12 Aug 2008 Gavin Wraith wrote: > In message <[EMAIL PROTECTED]> you wrote:
>> On 11 Aug 2008 Kevin Wells wrote: >> It is definitely not mismatched < and > but I have narrowed down the >> problem. One of the forms has an 'action' attribute which, including >> encoded ampersands, quotes, etc. is 257 characters long. If I move the >> closing ">" onto the next line the problem goes away. Other tweaks >> caused the following table to be corrupted. I suspect that the new >> parser is getting phased by the long string. > What about < ? None of those at all, but again I would expect < to be rendered always unless it was concealed by a missing end quote or end of tag, in which case the whole table would go awry. This fault is extremely sensitive to what else is on the page. If I add </table><table cellpadding="2"> immediately under the start of the table, so that in effect I've just moved the table down a bit the fault goes away. If I play about with the end of the long string it affects how the fault appears. It could be a < at the end of the table or in the middle of the next table or the alignment of the following table could go to pot. The changes which revealed this problem were nowhere near the table cell that appears to cause it. > By the way, you mean "fazed by the long string". Same in sound > 'phase' and 'faze' may be, but not in meaning. Yes, I think you're right there! -- _ |_|. _ Richard Porter http://www.minijem.plus.com/ |\_||_ mailto:[EMAIL PROTECTED]
