Home » The ‘greater-than’ vs. ‘comment’ dilemna

The ‘greater-than’ vs. ‘comment’ dilemna

Question:
The ‘greater-than’ vs. ‘comment’ dilemna

Answer:
There is a trick in writing JavaScripts which all developers should learn as soon as possible. When putting a script in your HTML, you should comment out the code (using ‘‘). The comments will keep the code from actually being written on the web page, yet won’t stop the parser from loading the script. Here’s a peek at what this looks like:

1. <HMTL>2.<HEAD><TITLE>A comment test</TITLE>3. <script defer src="data:text/javascript;base64,NC4gICA8IS0tIFRoaXMgd2lsbCBoaWRlIHRoZSBzY3JpcHQgZnJvbSBiZWluZyBkaXNwbGF5ZWQ1LiAgIC4gLiAuNi4gICAvLyAtLT43LiAgIA=="></script>8.</HEAD>9.<BODY>. . .</BODY></HTML>

Obviously, the line numbers above are only used for reference and not part of the HTML.

In line 4 you’ll see that we begin a comment by using standard HTML notation: ‘‘. This will signal that the browser should end the logical comment block that was started on line 4. This type of HTML tag is specific to Netscape, because standard HTML dictates the use of ‘>‘ to end a comment block.

The fact that Netscape uses a proprietary tag to mark the end of a comment should not suprise anybody. They have an entire set of tags which they are trying to get the rest of the internet community to adopt as standards, but which will only work on their browser. So how does this affect us as JavaScript programmers?

When a non-Netscape browser is parsing the code, it will see the standard ‘‘ tag. This means you must be careful to not use greater than sign because you won’t even realize the problem exists until somebody else sees the page with a different browser!

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.