Bug 46778

Summary: Implement XHR priority in WebCore
Product: WebKit Reporter: James Simonsen <simonjam>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: ahmad.saleem792, ap, cdumez, rniwa
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Bug Depends on: 43400    
Bug Blocks:    
Attachments:
Description Flags
Patch
none
Patch abarth: review-

James Simonsen
Reported 2010-09-28 20:10:37 PDT
Implement XHR priority in WebCore
Attachments
Patch (20.17 KB, patch)
2010-09-28 20:16 PDT, James Simonsen 		no flags
DetailsFormatted DiffDiff
Patch (27.00 KB, patch)
2010-10-07 14:22 PDT, James Simonsen 		abarth: review-
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
James Simonsen
Comment 1 2010-09-28 20:16:15 PDT
Created attachment 69157 [details] Patch
James Simonsen
Comment 2 2010-10-07 14:22:03 PDT
Created attachment 70150 [details] Patch
Adam Barth
Comment 3 2010-10-10 12:32:42 PDT
Comment on attachment 70150 [details] Patch We already have a loader prioritization mechanism: ResourceLoadScheduler. It seems like it would make more sense to integrate with that prioritization mechanism rather than rolling some XMLHttpRequest specific loader classes. Also, this bug does not explain why we want to do make this change.
Ahmad Saleem
Comment 4 2022-09-10 14:29:40 PDT
rniwa@webkit.org - Is this something needed because I think if I am right according to this MDN, it is non-standard and we can mark this as "RESOLVED WONTFIX"? Thanks! https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/1.5/Changing_the_priority_of_HTTP_requests
Ryosuke Niwa
Comment 5 2022-09-10 14:30:55 PDT
Yeah, this is Won't Fix at this point.
Note You need to log in before you can comment on or make changes to this bug.