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)

defect

Tracking

()

People

(Reporter: saschanaz, Unassigned)

References

Details

(Whiteboard: [necko-triaged][necko-priority-next])

https://searchfox.org/mozilla-central/rev/0dd776599d18cfc207a44dea24e8595f79a74755/dom/base/BodyConsumer.cpp#822-828

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?)

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
See Also: → 1908729

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.