W3C home > Mailing lists > Public > public-html@w3.org > May 2012

[Bug 16986] New: i18n-ISSUE-130: Health warning about no file-internal encoding in JS

From: <bugzilla@jessica.w3.org>
Date: Mon, 07 May 2012 18:23:14 +0000
To: public-html@w3.org
Message-ID: <bug-16986-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16986

           Summary: i18n-ISSUE-130: Health warning about no file-internal
                    encoding in JS
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: addison@lab126.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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 .

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 8 May 2012 18:13:27 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:52 UTC