536529 - Properly set nsIChannel.contentCharset according to @charset attribute in <script> element

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, defect)

Description

[Jan Honza Odvarko [:Honza] (always need-info? me)]

An issue related to charset was reported in Firebug.

http://code.google.com/p/fbug/issues/detail?id=429
when debugging an html file written in UTF-8, which contains <script> tags
who "point" to ISO-8859-1 encoded *.js files, firebug displays the contents
of such *.js files as gibberrish.

The problem is that if a JS file included using <scipt> element that specifies a charset, the underlying request _channel_ object (that is created to download the file) doesn't have set the nsIChannel.contentCharset property according to the value specified in the @charset attribute.

Example:

1) This JS file is using "ISO-8859-1"
<script type="text/javascript" src="dirrerentlyEncodedScriptFile.js"
charset="ISO-8859-1"/>

2) The appropriate _channel_ that is opened, should have set the contentCharset prop to "ISO-8859-1". But it's empty -> BUG.

Online test case:
http://getfirebug.com/tests/issues/429/index.xhtml

Related discussion
http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/9ed8df75aa4b1f86?hl=en#

Honza

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

DOM just needs to set the contentCharset before opening the channel

Comment 2

[Boris Zbarsky [:bzbarsky]]

So... As I later commented in the newsgroup, this is not documented on nsIChannel and doesn't work on channels in general (not even the ones Gecko ships by default).  So I don't think DOM can in fact do this.