This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16986 - i18n-ISSUE-130: Health warning about no file-internal encoding in JS
Summary: i18n-ISSUE-130: Health warning about no file-internal encoding in JS
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-07 18:23 UTC by Addison Phillips
Modified: 2012-05-08 16:07 UTC (History)
5 users (show)

See Also:


Attachments

Description Addison Phillips 2012-05-07 18:23:11 UTC
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 .
Comment 1 Ian 'Hixie' Hickson 2012-05-08 00:30:00 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: What would the warning say?