Questioning the Need for Type Attribute in Tags</strong></p> <p>While web servers are responsible for setting MIME types, the inclusion of the "type" attribute in <script> tags has sparked debate regarding its purpose and necessity.</p> <p><strong>Douglas Crockford's Perspective:</strong></p> <p>Douglas Crockford maintains that the "type" attribute is superfluous in XHTML and unnecessary in HTML. Browsers inherently recognize JavaScript as the default programming language, making it redundant. Omitting the attribute results in a more concise and universally compatible approach.</p> <p><strong>MIME Type Controversy:</strong></p> <p>The W3C opted for a "type" attribute that accepts MIME types. However, a lack of standardization means that MIME types for scripts vary, with options like "text/javascript" and "application/ecmascript." Thankfully, browsers consistently default to JavaScript, rendering the MIME type attribute largely irrelevant.</p> <p><strong>Experimental Evaluation:</strong></p> <p>To illustrate the compatibility of omitting the "type" attribute, five scripts were tested on Chrome and IE8:</p> <ul> <li><script type="application/ecmascript"> (1)</li> <li><script type="text/javascript"> (2)</li> <li><script type="baloney"> (3)</li> <li><script type=""> (4)</li> <li><script> (5)</li> </ul> <p>On Chrome, all but script 3 (with the invalid "baloney" type) executed successfully. IE8, however, failed to run scripts 1 (with the "application/ecmascript" type) and 3.</p> <p>Based on these limited tests, it appears that the "type" attribute can be safely omitted, although using a valid MIME type (browser dependent) is advisable if it is included.</p>
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
