Open
Bug 1848036
Opened 10 months ago
Updated 10 months 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
()
ASSIGNED
People
(Reporter: twisniewski, Assigned: twisniewski)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
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•10 months ago
|
||
|
||
Updated•10 months ago
|
Assignee: nobody → twisniewski
Status: NEW → ASSIGNED
|
||
Updated•10 months ago
|
Severity: -- → S3
Priority: -- → P3
Whiteboard: [necko-triaged]
You need to log in
before you can comment on or make changes to this bug.
Description
•