Closed
Bug 1410139
Opened 7 years ago
Closed 6 years ago
Failure in XMLHttpRequest/open-url-encoding.htm
Categories
(Core :: DOM: Networking, enhancement, P3)
Core
DOM: Networking
Tracking
()
RESOLVED
DUPLICATE
of bug 1460233
Tracking | Status | |
---|---|---|
firefox58 | --- | affected |
People
(Reporter: wisniewskit, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
This bug is a follow-up to bug 1405696, where we change XMLHttpRequest to pass the document charset into NS_NewURI to match a spec change.
This change causes us to behave differently to other engines on the second web platform test in XMLHttpRequest/open-url-encoding.htm. (Note that until bug 1405696 lands, we will appear to be passing this test).
We emit "&%2365533;" for the "lone surrogate" test while Blink/WebKit emit "%26%2355357%3B" and Edge emits "?". It's unclear to me whether we should be escaping the ampersand and semicolon as Blink/WebKit do.
Reporter | ||
Comment 1•7 years ago
|
||
Per bug 1405696 comment 33, it turns out that Firefox is doing the right thing after all for this test, so I'm closing this as invalid (and will ensure the correct expectation is set for this test when I check in the patch in that bug).
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Comment 2•6 years ago
|
||
In the end, in bug 140569 we decided to consider this "lone surrogate" test failure in its own bug, so I'm reopening this.
annevk, emk, did you have insight on what we need to do here?
Blocks: xhr
Status: RESOLVED → REOPENED
Flags: needinfo?(annevk)
Flags: needinfo?(VYV03354)
Resolution: INVALID → ---
Comment 4•6 years ago
|
||
Nothing; I didn't end up changing the test-case or Firefox's behavior, so we're still failing the WPT as it is (as is everyone except Chrome). Based on that and the comment you highlighted, I'm guessing that means the test should be altered to expect our behavior, but I figured it would be best to get a second opinion before doing so.
Comment 5•6 years ago
|
||
I should also note that we're not failing the same way that Webkit and Edge are, according to wpt.fyi: https://wpt.fyi/results/xhr/open-url-encoding.htm
Comment 6•6 years ago
|
||
This will be fixed once bug 1460233 is fixed. (That will also fix a large number of Encoding Standard tests, so if someone can take that on it'd be good for our wpt test score.)
Depends on: 1460233
Flags: needinfo?(annevk)
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Component: DOM → DOM: Networking
Priority: P3 → --
Updated•6 years ago
|
Priority: -- → P3
QA Contact: jduell.mcbugs
Whiteboard: [necko-triaged]
Updated•6 years ago
|
QA Contact: jduell.mcbugs
Updated•6 years ago
|
Status: REOPENED → RESOLVED
Closed: 7 years ago → 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•