Nightly regression on XHR from worker
Categories
(Core :: DOM: Security, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox64 | --- | unaffected |
firefox65 | --- | unaffected |
firefox66 | --- | fixed |
People
(Reporter: alonzakai, Assigned: jkt)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
Run a webserver like
python -m SimpleHTTPServer
with the two files attached, then browse to
http://localhost:8000/test.html
Actual results:
Looking in the web console, it shows
sending! http://localhost:8888/report_result?0
sent!
Looking in the network tab (and reloading), there is no network request sent to there, but the source code is
xhr.open('GET', url, !$1);
console.log('sending! ' + url);
xhr.send();
console.log('sent!');
so it should have been sent.
Expected results:
This is a regression in firefox nightly, I think in the last few days. It worked in older firefox and still works in chrome, that is, the network tab shows a network request sent as expected.
Noticed on Emscripten CI, which runs nightly (tests: browser.test_single_file_html, browser.test_single_file_worker_js; see https://github.com/emscripten-core/emscripten/pull/7895).
Comment 3•5 years ago
|
||
c:>mozregression --good=2019-01-10 --arg="https://matti.port0.org/bug1521239/test.html"
2:54.51 INFO: No more inbound revisions, bisection finished.
2:54.51 INFO: Last good revision: 177103817494df65f31adc379f46af1dac849d10
2:54.51 INFO: First bad revision: 9fedba33cfa3ceb88437433072951f26bf9f9a90
2:54.51 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=177103817494df65f31adc379f46af1dac849d10&tochange=9fedba33cfa3ceb88437433072951f26bf9f9a90
Comment 4•5 years ago
|
||
Recent regression, I think we should track that.
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
alonzakai thanks for the report, we have reverted the change in nightly so this should hopefully now be fixed. I will verify once the revert is merged back in.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Description
•