bug 801013 - imgRequest::AdjustPriority wrongly adjusts loadgroup instead of channel r=joedrew
--- a/image/src/imgRequest.cpp
+++ b/image/src/imgRequest.cpp
@@ -338,17 +338,17 @@ void imgRequest::AdjustPriority(imgReque
// XXX(darin): this is probably not the most optimal algorithm as we may want
// to increase the priority of requests that have a lot of proxies. the key
// concern though is that image loads remain lower priority than other pieces
// of content such as link clicks, CSS, and JS.
//
if (!GetStatusTracker().FirstConsumerIs(proxy))
return;
- nsCOMPtr<nsISupportsPriority> p = do_QueryInterface(mRequest);
+ nsCOMPtr<nsISupportsPriority> p = do_QueryInterface(mChannel);
if (p)
p->AdjustPriority(delta);
}
void imgRequest::SetIsInCache(bool incache)
{
LOG_FUNC_WITH_PARAM(gImgLog, "imgRequest::SetIsCacheable", "incache", incache);
mIsInCache = incache;