Open
Bug 1910124
Opened 3 months ago
Updated 3 months ago
BodyConsumer should not abort consumption when entering bfcache
Categories
(Core :: DOM: Networking, defect, P2)
Core
DOM: Networking
Tracking
()
NEW
People
(Reporter: saschanaz, Unassigned)
References
Details
(Whiteboard: [necko-triaged][necko-priority-next])
BodyConsumer currently aborts the consumption on window freeze (aka entering bfcache) but the page should kept intact when entering and leaving bfcache, and if that's impossible it should not enter bfcache at all.
(Unsure what to do here though, is it okay to continue reading for a frozen window? What happens when it finishes?)
Reporter | ||
Comment 1•3 months ago
|
||
This is technically related to FetchBody, so putting it in networking. (Although it's also being used for blob methods)
Component: DOM: Core & HTML → DOM: Networking
Comment 2•3 months ago
|
||
Like I said in this comment, it'd be faster for someone from DOM team to fix this.
Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-next]
You need to log in
before you can comment on or make changes to this bug.
Description
•