[Net] Assert that URLRequests with LOAD_IGNORE_LIMITS have MAXIMUM_PRIORITY

content/browser/loader/resource_scheduler.cc

Index: content/browser/loader/resource_scheduler.cc
diff --git a/content/browser/loader/resource_scheduler.cc b/content/browser/loader/resource_scheduler.cc
index d458936ecf1e29110a8a935fbcbcca3ad155f5a6..3c735aea646f10a0ef173471a443eb3e478edd5c 100644
--- a/content/browser/loader/resource_scheduler.cc
+++ b/content/browser/loader/resource_scheduler.cc
@@ -290,7 +290,8 @@ void ResourceScheduler::ReprioritizeRequest(ScheduledResourceRequest* request,
   }
 
   client->pending_requests.Erase(request);
-  client->pending_requests.Insert(request, request->url_request()->priority());
+  client->pending_requests.Insert(request,

[akalin, 2013/10/30 23:32:16]

should this also do InsertAtFront if ignore_limits is set?

[akalin, 2013/11/01 07:02:47]

Matt, any opinion here? Should I add a TODO?

[mmenke, 2013/11/01 15:48:00]

We shouldn't be reprioritizing those requests in the first place.  Could make
this class more aware of those requests, but I don't think that's the way to go
about it.

[akalin, 2013/11/01 18:50:15]

Ah, right. Added a check instead.

+                                  request->url_request()->priority());
 
   if (new_priority > old_priority) {
     // Check if this request is now able to load at its new priority.