Now requires Firefox 140 or later.

Security fixes:
- WebSocket connections are now blocked inside a quarantined container from the moment it is created. A page could previously keep a connection open through the network lock by holding it in a shared worker.
- Speculative DNS lookups (network prediction) are now turned off for the whole browser while a container is open, and restored when it closes. A page could otherwise leak data by looking up a hostname it chose.
- Network access stays blocked while the extension itself reloads.

Popup:
- New "Speculative DNS" row showing whether network prediction is on.
- The help dialog explains which settings are turned off browser-wide while a container is open.
- Opens faster, with no resize animation or scrollbars.

No new permissions. QuaranTab collects no data.

Fixes:
- Fix tracking of requests that are redirected by other extensions and Firefox shimming
- Fix addon icon would disappear due to missing asset
- Fix race condition on all requests closing during a state transition
- Fix race condition on displaying open request count on load

Changes:
- Display an informational message when page loads instead of Firefox's error page detailing an unreachable proxy. This was made possible by blocking onBeforeRequest which requires a new permission.
- In addition to blocking via non-existent proxy, also block via onBeforeRequest since we already requested this permission
- Fix attempted blocked connections counted towards connection counting causing a bogus flapping of status between secure and insecure

Fixes:
- Firefox tracking protection interfered with connection counting. Firefox shimmed requests don't fire webRequest.onComplete events making it seem a persistent connection to backend is open. Therefore Quarantab never reached quarantine state.
- Race condition on page loaded event listener
- Updated dependencies

I am excited to roll out these new changes:
- Blocking WebSockets, WebRTC, and long-polling HTTP requests
- Code is no longer minified
- Added several new permissions to perform additional blocking
- UI shows status of each type of blocking performed
- Bug bounty pool replenished

Permissions explained:
"proxy" - Required to cut-off network access to the website by routing requests to a non-existent Socks proxy
"tabs" - Required to re-open a tab in a new container
"cookies" - Required for manipulating Container data and clearing browser data for temporary containers
"contextualIdentities" - Required for creating/deleting Containers
* "privacy" - Required for temporarily disabling WebRTC globally
* "webRequest" - Required for monitoring active connections to determine when it's safe to use
* "scripting" - Required for injecting a content script for shutting down active connections
* "storage" - Required for keeping track of WebRTC initial enable state
"<all_urls>" - Required to intercept proxy web requests for all sites
(*) Indicates added permissions this release

More intuitive and easy to understand interface:
- Clearly see the two functionalities and status of isolating a website in a container and cutting off network access
- Ability to quarantine current tab or opening a new tab.