Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
<!-- <script type="text/javascript">/*<![CDATA[*/ c-- ;//]]></script> -->
When I have the above line in the <head> section of a plain html page, Firefox 3.5.5 renders the trailing –> as text. If I change c– to c- it doesn’t. Any ideas what’s going on here? I getting an artifact on my pages with this due to a very large script that’s been crunched. I can change the statement to c-=1 and avoid the problem for now but…. I’d like to know what bit/byte is biting my a$$.
This is due to Firefox implementing SGML (on which HTML was based) comments strictly. This will only occur when the document is loaded in standards mode (i.e. there is a DOCTYPE).
The first
<!starts a comment. The first--enters a section in which>characters are allowed. The second--(in your script) leaves the section in which>characters are allowed. The>at the end of</script>then ends the comment. The following-->is therefore no longer part of the the comment and gets rendered as text.See http://www.howtocreate.co.uk/SGMLComments.html for a comprehensive guide to the issue.
Its also worth noting that the HTML 4 Specification says that ‘authors should avoid putting two or more adjacent hyphens inside comments’ and the HTML 5 Specification says comments must not ‘contain two consecutive U+002D HYPHEN-MINUS characters (–)’.
The solution, as you’ve found, is to not include
--in the middle of a comment.