XMLP tripping over javascript &&
Reported by Nate | March 31st, 2009 @ 11:38 AM | in 1.0 Release
this is a problem when parsing and loading inline javascript.
the XMLP parser tries to interpret any javascript operator starting with & as an xml entity, and chokes, spitting out an error when encountering it. the document is still attempted to be loaded, though, and the inline js is truncated when written to a file, resulting in another error when the interpreter tries to load the shortened file.
there are 3 operators in javascript that start with an ampersand. &, &=, &&. I'm not quite sure about the best way to patch this.
Comments and changes to this ticket
-
Thatcher September 9th, 2009 @ 05:47 PM
- Milestone set to “1.0 Release”
- State changed from “new” to “open”
- Tag changed from “ampersand, entity, inline, parse, parser, script” to “ampersand, entity, inline, parse, parser, script”
- Assigned user set to “Thatcher”
Will try to get this fixed in the next couple of days. Thanks for reporting and sorry for the delay!
-
Thatcher September 9th, 2009 @ 06:14 PM
- State changed from “open” to “resolved”
i threw this check into our latest and the issue seems resolved
<script> function testXMLSpecialCharacters(){ if(true && true && 0>-1){ var f = 0&1; f&=1; } } </script>
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Nate
Thatcher