ISSUE-130: Health warning about no file-internal encoding in JS

Health warning about no file-internal encoding in JS

State:

CLOSED

Product:

html

Raised by:

Addison Phillips

Opened on:

2011-07-23

Description:

Please add comments to bugzilla:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=16986

4.3.1 The script element
http://www.w3.org/TR/html5/scripting-1.html#the-script-element

Talking about the <script> element. We find this description of 'charset':

--
The charset attribute gives the character encoding of the external script resource. The attribute must not be specified if the src attribute is not present. If the attribute is set, its value must be a valid character encoding name, must be an ASCII case-insensitive match for the preferred MIME name for that encoding, and must match the encoding given in the charset parameter of the Content-Type metadata of the external file, if any.
--

Not sure if there should be a health warning here. Note that, unlike CSS, JavaScript files have no file-internal encoding announcement .

Related Actions Items:

No related actions

Related emails:

1. Review of tracker issues for best practices (Part IV) (from addison@lab126.com on 2015-03-31)
2. Re: [I18N-ACTION-150] Review of HTML open issues (from ishida@w3.org on 2014-02-21)
3. [I18N-ACTION-150] Review of HTML open issues (from addison@lab126.com on 2014-02-18)
4. [Bug 16986] i18n-ISSUE-130: Health warning about no file-internal encoding in JS (from bugzilla@jessica.w3.org on 2012-05-08)
5. Re: HTML5 Comment disposition (from w3@norbertlindenberg.com on 2012-03-20)
6. I18N-ISSUE-130: Health warning about no file-internal encoding in JS [HTML5-prep] (from sysbot+tracker@w3.org on 2011-07-23)

Related notes:

Display change log