Make XMLHttpRequest.mozBackgroundRequest chrome-only

RESOLVED FIXED in mozilla33

Status

()

Core
DOM
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: Ms2ger, Assigned: Ms2ger)

Tracking

({dev-doc-complete, site-compat})

Trunk
mozilla33
dev-doc-complete, site-compat
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Comment hidden (empty)
(Assignee)

Comment 1

4 years ago
Created attachment 8451684 [details] [diff] [review]
Make XMLHttpRequest.mozBackgroundRequest chrome-only
Attachment #8451684 - Flags: review?(jst)
(Assignee)

Updated

4 years ago
Keywords: dev-doc-needed, site-compat

Updated

4 years ago
Attachment #8451684 - Flags: review?(jst) → review+
https://hg.mozilla.org/mozilla-central/rev/86a264cd9be8
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33

Comment 5

3 years ago
Hi, We are using mix background request property of xmlhttprequest to have asyc call, but same property has been removed in Firefox version 33. Due to this we are getting an issue of loosing cookies when closing browser without sign-out.

Comment 6

3 years ago
Please provide us an alternative way for above property.
(Assignee)

Comment 7

3 years ago
Mohan: this is not the right venue for such requests. You can make feature requests for XMLHttpRequest in the places listed under "Participate:" at <https://xhr.spec.whatwg.org/>.
(In reply to Mohan from comment #5)
> Hi, We are using mix background request property of xmlhttprequest to have
> asyc call, but same property has been removed in Firefox version 33. Due to
> this we are getting an issue of loosing cookies when closing browser without
> sign-out.

Web pages couldn't use mozBackground anyway. Setting mozBackground must have no effect even before Firefox 33. This bug just unexposed the useless property. If the site was broken because of the removal, it's just the site is doing something totally wrong. (maybe some bogus sniffing?)

Comment 9

3 years ago
(In reply to Masatoshi Kimura [:emk] from comment #8)

> Web pages couldn't use mozBackground anyway. Setting mozBackground must have
> no effect even before Firefox 33. This bug just unexposed the useless
> property. If the site was broken because of the removal, it's just the site
> is doing something totally wrong. (maybe some bogus sniffing?)

Was it actually useless? Was it not being used for XHR against 401 pages?

<https://code.google.com/p/chromium/issues/detail?id=31582>
(In reply to Michael Haufe from comment #9)
> Was it actually useless? Was it not being used for XHR against 401 pages?
> 
> <https://code.google.com/p/chromium/issues/detail?id=31582>

Google guys must have overlooked the sentence "Requires elevated privileges to access." (This sentence was present even before comment #4. [1])
According to the linked page [2], you can suppress the auth prompt by setting a dummy authentification header.

[1] https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest$compare?to=654311&from=653499
[2] https://code.google.com/p/chromium/issues/detail?id=31582#c21
You need to log in before you can comment on or make changes to this bug.