Yes, i know. But the problem is that the "author" of the bad XML is the browser itself. And it happens on all browsers. If you have in a text area (html, not flash) the following code: <p>this is < a test</p> (that is correctly handled by flash) and you read the content through javascript, you will get: <p>this is < a test</p>. And of course i could not expect all browsers in the market fix this error.
I´m in the process of doing some string parsing, but because i don´t want to reinvent the wheel... well, i wanted to know if someone already faced this problem and already write a fix. On Fri, 14 Oct 2005 13:32:05 -0300, John Giotta <[EMAIL PROTECTED]> wrote: > The only thing I can think of off the top of head it to ingest the > "XML" as Text. Then do some major string parsing. > > Unfortunately, the author of the bad XML should be wrapping content > not to be parsed in CDATA declaration. > > Example: > > <node><![CDATA[ <Text-and-not-a-node> ]]></node> > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
