FetchEventof an inline
The aforementioned APIs are new/expermiental and do not currently work on all browsers. Testing was done with the browsers below:
|Chrome 64||Full support|
|Firefox 58/59||Full support (requires activation of experimental flags)|
|iOS Safari 8||Unsupported|
|iOs Safari 11||Fetch support only. Service Workers unsupported|
|Mac Safari 11.0||Fetch support only. Service Workers unsupported|
|Mac Safari 11.1||Full Support|
|IE/Edge||Not tested (no device available)|
Prior to the recent addition of fetch(), the XMLHttpRequest.onprogress callback handler was traditionally used to show progress bars and progress indicators. The Fetch API is great and we should use it, but "onprogress" handlers are not currently implemented with Fetch. These examples allow us to leverage Fetch while providing users with immediate feedback during certain "loading" states. Progress indicators could be especially useful to users on slow networks.
This repository began as a proof of concept for showing progress indicators from Service Workers. Everything seemed to work out and a few important lessons and caveats were discovered:
ReadableStreamreaders when the user signals the cancelation/abort of a page load (e.g. pressing ESC, clicking stop button, invoking
abortevent does not seem to be firing on Chrome, Firefox, or Safari as defined in the HTML spec 7.8.12 Aborting a document load.
<img onabort>callbacks are not called.
window.onabortcallbacks are not called.
To properly exemplify progress indicators for slow downloads or large files, a small (100kb) JPEG is being served from a remote HTTP/2 Nginx server that limits download speeds. The buffer/packet size is also reduced to show smoother, or more frequent progress updates (more iterations of
read() would send fewer progress updates that result in choppy progress indicators. Caching is disabled to force network requests for repeated tests.
Both Baseline and Progressive JPEG files are available for testing with other speeds: