Closed
Bug 759624
Opened 13 years ago
Closed 7 years ago
Handling of user/password in XHR is not correct per spec
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
RESOLVED
DUPLICATE
of bug 1456421
People
(Reporter: bzbarsky, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
4.66 KB,
patch
|
Details | Diff | Splinter Review |
E.g. we treat "empty string" as "no value passed", which is not right.
![]() |
Reporter | |
Comment 1•13 years ago
|
||
But there are other issues too, afaict: we ignore the password if the user was not passed, say.
Comment 2•9 years ago
|
||
Ran into the comment while looking at other bugs. I don't know if this wasn't fixed because of compatibility problems or it's just that nobody bothered, but here's a patch. Changed the WPT because as far as I can tell there's nothing in the spec that supports those assertions, the logic is much simpler.
I don't know who to ask for review, everyone is either super busy or unavailable, so NI? myself to try again later.
Flags: needinfo?(reuben.bmo)
![]() |
Reporter | |
Comment 3•9 years ago
|
||
No one bothered, but that does not mean there are no compatibility problems. The first step here is figuring out what the behavior of current UAs is.
Updated•8 years ago
|
Keywords: dev-doc-needed
Updated•7 years ago
|
Priority: -- → P5
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(reuben.bmo)
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Keywords: dev-doc-needed
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•