Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
bu...@chromium.org <bu...@chromium.org> #3
[Empty comment from Monorail migration]
vp...@gmail.com <vp...@gmail.com> #4
This is still the case in Version 29.0.1547.62.
ag...@chromium.org <ag...@chromium.org> #5
thanks for reporting issue, can you please attach sample file/URL.
ro...@rwwc.co.uk <ro...@rwwc.co.uk> #6
I'm still experiencing this in Version 29.0.1547.66 m
ro...@rwwc.co.uk <ro...@rwwc.co.uk> #7
Simplified sample files attached
[Deleted User] <[Deleted User]> #8
Thanks for providing the info. Below are the steps I tried:
1. Open the index.htm file and click on choose files
2. Got upload window, selected file and clicked ok
3. File name is seen beside choose file button.
Same behavior is seen in other browser as well. Please explain the issue that you are seeing here.
1. Open the index.htm file and click on choose files
2. Got upload window, selected file and clicked ok
3. File name is seen beside choose file button.
Same behavior is seen in other browser as well. Please explain the issue that you are seeing here.
[Deleted User] <[Deleted User]> #9
@elarsson@gdssecurity.com: Could you please respond to Commnet7#
ro...@rwwc.co.uk <ro...@rwwc.co.uk> #10
The issue is not whether the file input field works, which of course it does, but as per the original submission by elarsson@gdssecurity.com that no progress event is fired from an XMLHttpRequest inside a web worker.
In order to test whether that works you would obviously need to have suitable endpoint for the XMLHttpRequest being started in the worker.js file etc. For this reason the code I attached has not even been tested and is a simplified example of the process to call a web worker and start and XMLHttpRequest within it.
I am naturally not going to post here publicly a URL to a server receiving uploads for you to test. I assume this is why the original reporter didn't provide a sample either.
In order to test whether that works you would obviously need to have suitable endpoint for the XMLHttpRequest being started in the worker.js file etc. For this reason the code I attached has not even been tested and is a simplified example of the process to call a web worker and start and XMLHttpRequest within it.
I am naturally not going to post here publicly a URL to a server receiving uploads for you to test. I assume this is why the original reporter didn't provide a sample either.
vp...@gmail.com <vp...@gmail.com> #11
Find attached a modified version of the above sample, with a simple PHP file included. Hopefully this helps to clarify the issue.
Running this in Firefox, the upload progress callback (which appends "Bytes loaded so far: ..." to the page) happens every ~50 or so milliseconds while a file is being sent. In Chrome, it never happens.
Running this in Firefox, the upload progress callback (which appends "Bytes loaded so far: ..." to the page) happens every ~50 or so milliseconds while a file is being sent. In Chrome, it never happens.
er...@sendsafely.com <er...@sendsafely.com> #12
@rponn...@chromium.org
As mentioned in #9 the issue is not that the upload doesn't work. The problem is that the two events xhr.upload.onprogress and xhr.onprogress are not called frequently as they are in Firefox. Since they are not, there is no good way to get progress updates back when doing larger uploads.
As mentioned in #9 the issue is not that the upload doesn't work. The problem is that the two events xhr.upload.onprogress and xhr.onprogress are not called frequently as they are in Firefox. Since they are not, there is no good way to get progress updates back when doing larger uploads.
ty...@chromium.org <ty...@chromium.org> #13
[Empty comment from Monorail migration]
dr...@gmail.com <dr...@gmail.com> #14
Any updates on this? As I'm having exactly the same issues.
I'm running an XMLHttpRequest from a web worker, and i'm only getting one progress event fired at the end of the file chunk upload. Firefox it works as expected.
Thanks!
I'm running an XMLHttpRequest from a web worker, and i'm only getting one progress event fired at the end of the file chunk upload. Firefox it works as expected.
Thanks!
bu...@chromium.org <bu...@chromium.org> #16
The following revision refers to this bug:
http://src.chromium.org/viewvc/blink?view=rev&rev=161923
------------------------------------------------------------------------
r161923 | sigbjornf@opera.com | 2013-11-13T15:09:21.041074Z
Changed paths:
Ahttp://src.chromium.org/viewvc/blink/trunk/LayoutTests/http/tests/xmlhttprequest/workers/upload-onprogress-event.html?r1=161923&r2=161922&pathrev=161923
Ahttp://src.chromium.org/viewvc/blink/trunk/LayoutTests/http/tests/xmlhttprequest/workers/resources/upload-onprogress-event.js?r1=161923&r2=161922&pathrev=161923
Mhttp://src.chromium.org/viewvc/blink/trunk/Source/platform/network/ResourceRequest.cpp?r1=161923&r2=161922&pathrev=161923
Mhttp://src.chromium.org/viewvc/blink/trunk/Source/platform/network/ResourceRequest.h?r1=161923&r2=161922&pathrev=161923
Ahttp://src.chromium.org/viewvc/blink/trunk/LayoutTests/http/tests/xmlhttprequest/workers/resources/upload-onprogress-worker.js?r1=161923&r2=161922&pathrev=161923
Ahttp://src.chromium.org/viewvc/blink/trunk/LayoutTests/http/tests/xmlhttprequest/workers/upload-onprogress-event-expected.txt?r1=161923&r2=161922&pathrev=161923
Enable XHR upload progress events for Workers.
The request flag recording progress event reporting wasn't been copied
out of the worker when creating the loader on the main thread. Do so
to have upload progress events be reported over XMLHttpRequest inside
a Worker.
R=
BUG=173658
Review URL:https://codereview.chromium.org/71433002
------------------------------------------------------------------------
------------------------------------------------------------------------
r161923 | sigbjornf@opera.com | 2013-11-13T15:09:21.041074Z
Changed paths:
A
A
M
M
A
A
Enable XHR upload progress events for Workers.
The request flag recording progress event reporting wasn't been copied
out of the worker when creating the loader on the main thread. Do so
to have upload progress events be reported over XMLHttpRequest inside
a Worker.
R=
BUG=173658
Review URL:
------------------------------------------------------------------------
[Deleted User] <[Deleted User]> #18
[Empty comment from Monorail migration]
dr...@gmail.com <dr...@gmail.com> #19
What version will this fix appear in?
[Deleted User] <[Deleted User]> #20
If you want to test, canary builds has the fix (e.g., 33.0.1726.0)
tk...@chromium.org <tk...@chromium.org> #21
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]> #22
[Deleted User] <[Deleted User]> #23
is...@google.com <is...@google.com> #24
This issue was migrated from crbug.com/chromium/173658?no_tracker_redirect=1
[Monorail mergedwith:crbug.com/chromium/106705 ]
[Monorail components added to Component Tags custom field.]
[Monorail mergedwith:
[Monorail components added to Component Tags custom field.]
Description
Chrome Version : 24.0.1312.57
URLs (if applicable) :
Other browsers tested:
Firefox 18.0.1: OK
What steps will reproduce the problem?
var xhr = new XMLHttpRequest();
xhr.open('POST', "www.example.com/upload/", true);
xhr.onprogress = function(e) {
// Do stuff
};
xhr.upload.onprogress = function(e) {
// Never called when executed from a worker.
};
xhr.onload = function(e) {
// Do stuff
};
xhr.send(data);
The upload progress will be displayed.
2. Load the same snippet in a web worker, the progress callback will never be invoked.
What is the expected result?
To get upload progress on your current file upload.
What happens instead?
No progress is displayed.