Yeah, those messages make sense I think... I guess FF realizes that your trying to eval something that's purely markup and tries to parse it as XML... incorrect nesting of the tags in the first case makes sense for that message, as no closing tag makes sense for the second, if it were trying to parse it. I guess maybe it examines the contents your eval'ing and differentiates between pure markup and script? Interesting!
Frank -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM/Yahoo: fzammetti MSN: [EMAIL PROTECTED] Author of "Practical Ajax Projects With Java Technology" (2006, Apress, ISBN 1-59059-695-1) Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! On Wed, November 29, 2006 7:48 am, Dave Newton wrote: > From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] >> (interestingly, in IE I get a syntax error, because it's trying to >> interpret the markup as script, but in FF it just quietly doesn't >> work, not even a notice in Firebug). > > Something else interesting in FF: > > eval("<foo><bar></foo></bar>") > > "XML tag name mismatch" > > eval("<foo>") > > "unexpected end of XML source" > > Dave > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
