1035242 - Make XMLHttpRequest.mozBackgroundRequest chrome-only

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Comment 1

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

Attachment: Make XMLHttpRequest.mozBackgroundRequest chrome-only

Comment 2

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

https://hg.mozilla.org/integration/mozilla-inbound/rev/86a264cd9be8

Comment 3

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/86a264cd9be8

Comment 4

[Jean-Yves Perrier [:teoli]]

Doc changed:
https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest
https://developer.mozilla.org/en-US/Firefox/Releases/33
https://developer.mozilla.org/en-US/Firefox/Releases/33/Site_Compatibility

Comment 5

[Mohan]

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

[Mohan]

Please provide us an alternative way for above property.

Comment 7

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

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/>.

Comment 8

[Masatoshi Kimura [:emk]]

(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

[Michael Haufe]

(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>

Comment 10

[Masatoshi Kimura [:emk]]

(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