html - Using type="textplain" for JavaScript? - Stack Overflow

admin管理员组

文章数量:1195166

I was looking at setting this up, simply out of curiosity, however I was a little bemused when they stated for this to work you need to:

Find any Javascript elements that set Analytics cookies. Examples might include Google Analytics and StatCounter. Modify the script tag so that the type attribute is "text/plain" rather than "text/javascript"

Would this cause any problems with certain web browsers? Would it cause the HTML to no longer validate?

Also, does the "type" attribute even really serve a purpose anymore? I've only ever seen it assigned "text/JavaScript" before?

I was looking at setting this up, simply out of curiosity, however I was a little bemused when they stated for this to work you need to:

Find any Javascript elements that set Analytics cookies. Examples might include Google Analytics and StatCounter. Modify the script tag so that the type attribute is "text/plain" rather than "text/javascript"

Would this cause any problems with certain web browsers? Would it cause the HTML to no longer validate?

Also, does the "type" attribute even really serve a purpose anymore? I've only ever seen it assigned "text/JavaScript" before?

• javascript
• html

Share Improve this question Follow edited May 27, 2013 at 21:58 Sean asked Aug 23, 2012 at 11:49 SeanSean 6,49999 gold badges4949 silver badges7070 bronze badges

Add a comment  | 

3 Answers 3

Sorted by: Reset to default 19

It does not cause problems, if the intent is that browsers do not interpret the content of the element as script code but just as text data that is not rendered. It’s there for scripts to use it, but otherwise it’s ignored. Well, in some browsers, the content might be made visible using CSS, but by default it’s not shown.

Using <script type="text/plain"> is valid by HTML specs. Even <script type="Hello world ☺"> is valid, though it violates the prose requirement that the attribute value be a MIME type. The specs do not specify its meaning, but the only feasible interpretation, and what browsers do in practice, is that it is not in any scripting language and no execution as script is attempted.

So type="text/plain" may be used to intentionally prevent execution of a script, while still keeping it in the source. It may also be used to carry bulks of character data used for some processing.

The type attribute may serve purposes like this, and it can also be used to specify scripting languages other than JavaScript (rarely used, but still possible in some environments). Using the type attribute just to specify JavaScript is not needed, and cannot be recommended: the only thing that you might achieve is errors: if you mistype, e.g. type="text/javascirpt", the content will be regarded as being in an unknown language, hence ignored.

Would this cause any problems with certain web browsers?

No

Would it cause the HTML to no longer validate?

No

Also, does the "type" attribute even really server a purpose anymore?

Browsers use it to decide what interpretor to run code through (or if they should download externally srced code at all).

Setting it to text/plain sets it to a type that browsers won't have interpretors for (since it isn't a programming language), which is the point.

Giving JS code the text/plain type is perfectly ok and will effectively disable it. To enable the script after the page was loaded you will need to have JS code to rewrite the type to text/javascript on the fly. Cookie blocking is a common example. Insert a cookie-setting script with text/plain and change to text/javascript when the user gives cookie consent. This will execute the script immediately, on the current page, no need to reload it.

本文标签： htmlUsing typequottextplainquot for JavaScriptStack Overflow