This adds a new set of signals, produced by webkit's ImageLoader, that fires when an asset begins loading and when it finishes.
This is used because ImageLoader side-steps QNetworkAccessManager when there is a concurrent request in progress for the same asset, causing issues with us being able to calculate in-flight. By hooking up the assetStarted and assetFinished signals, we can keep a second inFlightRequests list to see if that particular image is loading at a given time.
This adds a new set of signals, produced by webkit's
ImageLoader, that fires when an asset begins loading and when it finishes.This is used because
ImageLoaderside-stepsQNetworkAccessManagerwhen there is a concurrent request in progress for the same asset, causing issues with us being able to calculate in-flight. By hooking up theassetStartedandassetFinishedsignals, we can keep a secondinFlightRequestslist to see if that particular image is loading at a given time.