7752 2009-09-29 12:59:12 +0000 Please use "URL character encoding" instead of just "character encoding" for clarity 2010-10-04 14:54:56 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other CLOSED FIXED http://www.whatwg.org/specs/web-apps/current-work/#creating-scripts P3 normal LC 1 contributor ian annevk ian mike public-html-admin public-html-wg-issue-tracking zcorpan public-html-bugzilla oldest_to_newest 27852 0 contributor 2009-09-29 12:59:12 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#creating-scripts Comment: Please use "URL character encoding" instead of just "character encoding" for clarity Posted from: 213.236.208.22 27976 1 zcorpan 2009-10-01 14:28:44 +0000 I don't see this being fixed in the spec? The relevant paragraph is "When the specification says that a script is to be created, given some script source, its scripting language, a global object, a browsing context, a character encoding, and a base URL, the user agent must run the following steps:" ...and then all instances that point to "creating a script" (including in Web Workers) should say "URL character encoding" instead of "character encoding". (I'm fine with having this bug fixed LATER than LC.) 27986 2 annevk 2009-10-01 18:41:32 +0000 There was a change regarding this, but not the one you were looking for: http://html5.org/tools/web-apps-tracker?from=4058&to=4059 28445 3 ian 2009-10-18 10:24:47 +0000 Oops, didn't realise how many fixes this needed. Sorry about that. 28446 4 contributor 2009-10-18 10:37:20 +0000 Checked in as WHATWG revision r4166. Check-in comment: call the script's character encoding the URL character encoding. http://html5.org/tools/web-apps-tracker?from=4165&to=4166