One thing I have encountered with the new HTML parser is that it
doesn't like woconditional blocks if you open a tag within the
condition and close it outside. (think if/else). I was doing this in
a few places and it was having kittens about it. I have now
refactored the markup to use a WOGenericContainer and WOOgnl
expressions to do the conditional handling instead. This makes the
HTML cleaner, and it parses fine too.
On 09/05/2007, at 12:46 AM, Mike Schrag wrote:
> I suspect it means there is an unclosed tag inside that is tripping
> it up ... What build are you using? These validations have gone
> through several iterations, so maybe you have an older build.
>
> Basically I'm parsing templates with a funky crazy xml parser that
> tries to recover from horribly broken xml, but once you have a
> malformed document, it becomes a big guessing game to try and give
> you an error that makes sense because no matter what rule you pick,
> you will break some other scenario.
>
> If you don't see the problem after updating, please email me the
> html file so I can add it to my test cases.
>
> ms
>
> On May 8, 2007, at 10:34 AM, John Huss wrote:
>
>> In my page I have:
>>
>> <body onload="document.form.user.focus();">
>> .
>> .
>> .
>> </body>
>>
>> The problems view says: "<body> start tag is not found."
>>
>> Is there a way to fix that?
>>
>> Thanks,
>> John
>
>
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia Ph: +61 419 729 806
This archive was generated by hypermail 2.0.0 : Tue May 08 2007 - 11:11:34 EDT