Closed Bug 1378356 Opened 7 years ago Closed 7 years ago

Don't throttle pages with active network connections

Categories

(Core :: DOM: Core & HTML, enhancement, P1)

enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: farre, Assigned: farre)

References

Details

Attachments

(1 file)

      No description provided.
Blocks: 1377766
I need to still understand why we don't want to throttle pages with active network connections.
Since for throttling, why does it matter whether there are network connections open?
I do understand we need that for freezing a tab, but throttling isn't freezing.
And this means we end up throttling less than what we have done for years.
Comment on attachment 8883875 [details] [diff] [review]
0001-Bug-1378356-Don-t-throttle-pages-with-active-network.patch

Since I don't understand the reasoning, can't really review.
Attachment #8883875 - Flags: review?(bugs)
(In reply to Olli Pettay [:smaug] from comment #3)
> Since for throttling, why does it matter whether there are network
> connections open?
> I do understand we need that for freezing a tab, but throttling isn't
> freezing.

This is a valid point, maybe this isn't the right thing to do. Especially since we're only throttling timeouts and not all events. It should allow us to be more aggressive.
Assignee: nobody → afarre
Priority: -- → P1
(P1 but discussion here obviously trumps that)
This is not the right thing to do. Non-WebSockets network connections should be handled by handlers in any case.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: