Bugzilla

 > > I agree the behaviour should be consistent. I think if we only always want to get 1 image request in the devtool, then bomsy's fix is correct. However, if we want to always get multiple requests in the devtool, then we probably need to fix how we fire `http-on-image-cache-response`, perhaps it should be moved to `imgRequestProxy::OnLoadComplete`.
> 
> It sounds like you don't have a strong opinion here? I imagine that platform developers may have different point of view than web developers.
> Showing absolutely all image loads may be useful to debug platform issues, while it might be confusing for web developers who have more interest about actual network requests.
> Given that, the current fix is probably our best option, which we can easily revisit later if we want to display all image usages.

A good tradeoff might be showing some information indicating that this request is one of a number of requests (maybe some information in the tooltip). This might help platform developers.

 > > I agree the behaviour should be consistent. I think if we only always want to get 1 image request in the devtool, then bomsy's fix is correct. However, if we want to always get multiple requests in the devtool, then we probably need to fix how we fire `http-on-image-cache-response`, perhaps it should be moved to `imgRequestProxy::OnLoadComplete`.
> 
> It sounds like you don't have a strong opinion here? I imagine that platform developers may have different point of view than web developers.
> Showing absolutely all image loads may be useful to debug platform issues, while it might be confusing for web developers who have more interest about actual network requests.
> Given that, the current fix is probably our best option, which we can easily revisit later if we want to display all image usages.

Maybe a good tradeoff might be showing some information indicating that this request is one of a number of requests (maybe some information in the tooltip). This might help platform developers.