in reply to Apache2::UploadProgress & Safari bug status??

I recently hit this same problem myself, and found that it not only doesn't work with Safari, but also Chrome.
After much head-banging (and significant help from a co-worker), I did find a work-around.

Edit the file /extras/progress.js, and modify line 85 as follows:

- req.open('GET', url, Boolean(handleUploadProgressResults)); + req.open('GET', url, false);

It appears that the call to handleUploadProgressResults will always return true in Chrome/Safari. No idea why, but modifying (hardcoding) this to false does get things working.

cheers,
Darren

Replies are listed 'Best First'.
Re^2: Apache2::UploadProgress & Safari bug status??
by tlhackque (Beadle) on Feb 11, 2013 at 14:04 UTC
    I don't dispute the observation, but neither the original code nor the patch makes sense. At that line, handleUploadProgressResults is NOT called; it's a reference which will be non-null, hence the Boolean will be true. It's a convoluted way of expressing 'true'. That argument to XMLHttpRequest() *should* be true - false makes the request blocking (synchronous), which is always a bad idea as it can hang the browser. If false makes the code work, something else is broken. Perhaps there is some global variable that should be in a closure. This needs more investigation...

    This communication may not represent my employer's views, if any, on the matters discussed.