Closed
Bug 1848036
Opened 2 years ago
Closed 1 year ago
Add an ability to determine if it's safe to call an nsIRequest's suspend method
Categories
(Core :: DOM: Networking, defect, P3)
Core
DOM: Networking
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: twisniewski, Assigned: twisniewski)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 obsolete file)
Some nsIRequest subclasses, such as DocumentChannel, will simply crash whenever an attempt is made to call their Suspend method. This is bad for fixing bug 697151, where we need to try to suspend all of the channels we can in the same doc or loadgroup as a synchronous XMLHttpRequest. As such, it would be good to have another XPCOM on nsIRequests (perhaps canSuspend) which simply lets us know whether it's safe to even try to suspend a given channel in a doc/loadgroup.
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
Assignee: nobody → twisniewski
Status: NEW → ASSIGNED
|
||
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P3
Whiteboard: [necko-triaged]
|
|
Assignee | |
Comment 2•1 year ago
|
||
This should be unnecessary now, as we found a different approach to fix bug 697151.
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
|
|
||
Updated•11 months ago
|
Attachment #9348307 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•