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 25090 - Use document's encoding for url query encoding in XHR open()
Summary: Use document's encoding for url query encoding in XHR open()
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: XHR (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard: blocked on implementers weighing in
Keywords:
Depends on: 23822
Blocks:
  Show dependency tree / graph
 
Reported: 2014-03-18 13:37 UTC by Simon Pieters
Modified: 2014-10-27 17:16 UTC (History)
2 users (show)

See Also:

Attachments

Description Simon Pieters 2014-03-18 13:37:21 UTC 
http://xhr.spec.whatwg.org/#sync-warning

[[
Let parsedURL be the result of parsing url with base.
]]

Given the resolution in https://www.w3.org/Bugs/Public/show_bug.cgi?id=23822 I guess we should change XHR. (WebKit/Blink already use the document's encoding for XHR.)
Comment 1 Anne 2014-10-21 13:36:26 UTC 
If it's only Blink/WebKit, it seems given the resolution of the bug this depends on we should WONTFIX this as well.
Comment 2 Simon Pieters 2014-10-27 17:10:15 UTC 
That's OK. It's not clear to me what our story is for new APIs going forward but I guess we can decide that on a case-by-case basis. Or it will just be that Hixie APIs use the document's encoding and everything else uses utf-8. :-P
Comment 3 Anne 2014-10-27 17:16:06 UTC 
Well, why don't you bring this up at the next Blink F2F or some such? Maybe they're willing to take a stance here one way or another and everyone else can follow.