It is proprietary and unneeded as far as I can tell. And per bug 681931 might be leaking?
Seems to be used when people don't want a content-type set. See bug 416178 comment 31
You should get the same behavior per spec if you pass a Blob without a type to send(). But yes, we should warn about this going away first.
I agree. lets warn about this for a release or two and then nuke it. But we should be prepared to put it back temporarily if it's breaking high usage websites.
Depends on: 939323
OS: Mac OS X → All
Hardware: x86 → All
It seems this has been deprecated since Firefox 31. Time to remove it?
Whiteboard: [good first bug]
Created attachment 8561031 [details] [diff] [review] Initial version of patch Initial version of a patch, pretty much just grepping through the source and removing stuff that seems related.
Assignee: nobody → dirkjan
Status: NEW → ASSIGNED
Attachment #8561031 - Flags: review?(Ms2ger)
Comment on attachment 8561031 [details] [diff] [review] Initial version of patch Asking smaug to review based on comment from Ms2ger.
Attachment #8561031 - Flags: review?(Ms2ger) → review?(bugs)
Comment on attachment 8561031 [details] [diff] [review] Initial version of patch Could we land this for FF39, so that ESR38 would still have the warning - just in case some intranet site uses the property. Update uuid of nsIXMLHttpRequest.
Attachment #8561031 - Flags: review?(bugs) → review+
So I should just bump the UUID and then we'll hold off for two more weeks?
Pushed to try with updated UUID: https://hg.mozilla.org/try/rev/d73752326327 https://treeherder.mozilla.org/#/jobs?repo=try&revision=d73752326327
Created attachment 8568993 [details] [diff] [review] Patch with updated UUID Add new patch for landing.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
status-firefox39: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
You need to log in before you can comment on or make changes to this bug.