Add a new browser->tab event that signals eminent hibernation

[Ford_Prefect]

Why: Energy saving is a huge goal and on some devices a crucial necessity. Hibernating tabs that have not been recently used, seem to be one option that is promessing. But some webpages rely on uninterrupted running and might fail to work if they are frozzen in a state for hibernation and resumed later. A good solution could be, to provide a NEW browser event that is send to a tab/webpage, indicating eminent hibernation/freezing.

The event would provide Callbacks for

• requesting hibernation delay (within allotment of the browser), providing a method for the tab/webpage to bring its affairs in order.
• signaling 'ready'.

The request for delay could be presented to the user, allowing the user to add a tab/domain to an exemption list or do $foobar.

Example:

• Webpage that allows content creation locally, but saves data in the cloud. On event signal, it could request a delay, then save the data on local browser storage or even could try to save it to cloud.
• Terminating connection/stream to server
• Termination of cloud calculation
• ...

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

[Jon]

Thanks @Ford_Prefect!

Potentially related ideas here:

Firefox should suspend tabs to better performance 

Energy saving tabs 

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

[Ford_Prefect]

After thinking about it some more, there should actually be two new events.

1. notice of imminent state {hybernation} ... like in the idea above, with callbacks and such.
2. notice of resurrection from {state} ... informs a tab that it has been hybernated and is now been resumed. Tabs can do with that knowledge what they have to...

Naming schema:
A nother aspect, the metaphor "hybernation" suggests that some slowed down (metabolic) activity is still happening, while what is intended is more of a "freeze". Depending on implementation this should be considered. Maybe a multilevel approach with increasing limitations is favorable: normal --> hibernation --> freeze ... where hibernation is more of a optional self-controled behavior of tabs based on and controlled by browser events (indented as a hint that energy/resource saving behavior should be applied), while freeze is the browser enforced top-down-approach.