bug 801013 - imgRequest::AdjustPriority wrongly adjusts loadgroup instead of channel r=joedrew
authorPatrick McManus <mcmanus@ducksong.com>
Sat, 13 Oct 2012 12:47:36 -0400
changeset 110296 b8e7df7ac70f75b1564a5c25cf4cda1f2d71f5bb
parent 110295 34b1f3ed81136a0810d2f936b78ec75d9df50e2f
child 110297 5a5563b58d5b6cd059f4a77f8395b9dc6795ee1a
push id93
push usernmatsakis@mozilla.com
push dateWed, 31 Oct 2012 21:26:57 +0000
reviewersjoedrew
bugs801013
milestone19.0a1
bug 801013 - imgRequest::AdjustPriority wrongly adjusts loadgroup instead of channel r=joedrew
image/src/imgRequest.cpp
--- 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;