问题
I am trying to debug a JavaScript script that gets read in a Firefox extension and executed. I only can see errors via the Firebug console (my code is invisible to Firebug), and it's reporting a "unterminated string literal."
I checked the line and the lines around it and everything seems fine-parentheses, braces, and quotes are balanced, etc. What are other possible causes that I should be looking for?
回答1:
Most browsers seem to have problems with code like this:
var foo = "</script>";
In Firefox, Opera and IE8 this results in an unterminated string literal error. Can be pretty nasty when serializing html code which includes scripts.
回答2:
Look for linebreaks! Those are often the cause.
回答3:
I would vote for jamtoday's answer if I had the "reputation"
If your data is coming by way of PHP, this might help
$str = str_replace(array("\r", "\n"), '', $str);
回答4:
I just discovered that "<\/script>" appears to work as well as "</scr"+"ipt>".
回答5:
You might try running the script through JSLint.
回答6:
Just escape your tag closures or use ascii code
ie
<\/script>
ie
</script>
回答7:
Look for a string which contains an unescaped single qoute that may be inserted by some server side code.
回答8:
If you've done any cut/paste: some online syntax highlighters will mangle single and double quotes, turning them into formatted quote pairs (matched opening and closing pairs). (tho i can't find any examples right now)... So that entails hitting Command-+ a few times and staring at your quote characters
Try a different font? also, different editors and IDEs use different tokenizers and highlight rules, and JS is one of more dynamic languages to parse, so try opening the file in emacs, vim, gedit (with JS plugins)... If you get lucky, one of them will show a long purple string running through the end of file.
回答9:
Have you escaped your forward slashes( / )? I've had trouble with those before
回答10:
I've had trouble with angled quotes in the past ( ‘ ) usually from copy and pasting from Word. Replacing them with regular single quotes ( ' ) does the trick.
回答11:
Also, keep in mind that %0A is the linefeed character URL encoded. It took me awhile to find where there was a linefeed in my offending code.
回答12:
If nothing helps, look for some uni-code characters like
\u2028
this may break your string on more than one line and throw this error
回答13:
Maybe it's because you have a line break in your PHP code. If you need line breaks in your alert window message, include it as an escaped syntax at the end of each line in your PHP code. I usually do it the following way:
$message = 'line 1.\\n';
$message .= 'line 2.';
回答14:
Have you tried Chromebug? It's the Firebug for extensions.
回答15:
Try a "binary search". Delete half the code and try again. If the error is still there, delete half the remaining code. If the error is not there, put what you deleted back in, and delete half of that. Repeat.
You should be able to narrow it down to a few line fairly quickly. My experience has been that at this point, you will notice some stupid malformed string.
It may be expedient to perform this on a saved version of the HTML output to the browser, if you're not sure which server-side resource the error is in.
回答16:
The web page developer guessed wrong about which encoding is used by the viewer's browser. This can usually be solved by specifying an encoding in the page's header.
回答17:
Scan the code that comes before the line# mentioned by error message. Whatever is unterminated has resulted in something downstream, (the blamed line#), to be flagged.
回答18:
Whitespace is another issue I find, causes this error. Using a function to trim the whitespace may help.
回答19:
$str = str_replace(array("\r\n","\n\r","\r", "\n"), '
', stripslashes($str));
This should work.
来源：https://stackoverflow.com/questions/227552/common-sources-of-unterminated-string-literal